Skip to content

Persist the 1st report of worker - #127

Merged
sylvinus merged 1 commit into
pricingassistant:masterfrom
ecebuzz:master
Dec 9, 2016
Merged

Persist the 1st report of worker#127
sylvinus merged 1 commit into
pricingassistant:masterfrom
ecebuzz:master

Conversation

@ecebuzz

@ecebuzz ecebuzz commented Aug 11, 2016

Copy link
Copy Markdown
Contributor

I would like to see that the 1st report is persisted in the mongodb just like the last report in work_stop()

I would like to see that the 1st report is persisted in the mongodb just like the last report in work_stop()
@sylvinus

Copy link
Copy Markdown
Contributor

Hi @ecebuzz !

Interesting idea, can you explain why you'd want to see it?

@ecebuzz

ecebuzz commented Aug 11, 2016

Copy link
Copy Markdown
Contributor Author

I found that during the runtime of short jobs whose execution time is less than the report interval, mongodb queries for those jobs will not show any results until the very end when those short jobs finish and stop. Perhaps it is not the recommended way to query runtime information of the jobs. Perhaps I should change to query redis instead of mongodb.

@ecebuzz

ecebuzz commented Aug 11, 2016

Copy link
Copy Markdown
Contributor Author

It seems the change does not quite help. Does mrq dashboard query redis for the job and worker status?

@sylvinus
sylvinus merged commit 1e84646 into pricingassistant:master Dec 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants