Persist the 1st report of worker #127
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I would like to see that the 1st report is persisted in the mongodb just like the last report in work_stop()
|
Hi @ecebuzz ! Interesting idea, can you explain why you'd want to see it? |
|
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. |
|
It seems the change does not quite help. Does mrq dashboard query redis for the job and worker status? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I would like to see that the 1st report is persisted in the mongodb just like the last report in work_stop()