Worker status/monitoring for competition organizers (from rabbit)#2395
Open
IdirLISN wants to merge 46 commits into
Open
Worker status/monitoring for competition organizers (from rabbit)#2395IdirLISN wants to merge 46 commits into
IdirLISN wants to merge 46 commits into
Conversation
IdirLISN
changed the title
Didayolo
changed the title
Member
|
Very nice. We need to find a way to stress test this feature on a preprod environment. |
IdirLISN
force-pushed
the
feature/worker_monitoring
branch
from
aa78dae to
9f0e970
Compare
Member
|
Last TODO: Update the documentation https://docs.codabench.org/latest/Organizers/Running_a_benchmark/Competition-Detail-Page/ |
Didayolo
changed the title
IdirLISN
force-pushed
the
feature/worker_monitoring
branch
from
0cb63d8 to
bfcb136
Compare
…isibile only by admin or comp organizer or collaborators
* backend & frontend OK / TODO: site worker and leaderboad * site worker sending submissions to group queue OK * leaderboad group feature * logs removed * fix json leaderboard * Clean up leaderboard ordering logic * competition queue on groups with out queue * some bugfix * UI bugfix * UI bugfix * leaderboard groups format parentsubID_groupname * fix conflicts issues * resolve conflict * clean site worker * branch update and linter fix * linter fix * linter fix * linter fix * bugfix group form * adding migrations files * fix logic to fix tests problem * fix logic to fix tests problem * E2E test fixed * E2E test fixed * E2E test fixed * E2E test fixed * Fix queue name in server status * fix queues visibility * fix queue visibility for groups * Flake8 --------- Co-authored-by: didayolo <adrien.pavao@gmail.com>
IdirLISN
force-pushed
the
feature/worker_monitoring
branch
from
ccef98f to
7100d79
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
/!\ New PR with modified feature. /!\
The feature is now aware of workers health directly from django to rabbit instead of going through the site worker which slows the app massively. Using rabbit enable the feature to be much more responsive and display the worker state faster. the implementation is easier also.
check the feature at: https://dev.codabench.org/
------------------------------- OLD PR (edited) --------------------------------------
@ mention of reviewers
@ObadaS
@Didayolo
@ihsaan-ullah
Description
This feature enables admin users, competition organisers and his/her collaborators to monitor compute worker activity.
Public compute workers displayed by default and if the competition own a private queue, it displays the private compute workers linked to the queue of the competition.
UI inside of the header of the competition page.
Feature contains:
Feature available only for competition organizers and collaborators.
When disabled or hided behind the button, the websocket connection is disabled for performance.
Issues this PR resolves
Enables organizers to monitor compute workers activity to push them to use their own workers in case of high activity on codabench public compute workers.
A checklist for hand testing
(docker compose logs -f django should display websocket open and close with the panel)
Checklist