Enforcing correct task completion time using priority queue #93
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
sukritkalra
approved these changes
Mar 23, 2024
rpc/service.py
Outdated
|
|
||
| return erdos_scheduler_pb2.NotifyTaskCompletionResponse( | ||
| success=True, | ||
| message=f"Task with ID {request.task_id} completed successfully!", | ||
| message=f"Task with ID {request.task_id} completed successfully! " | ||
| f"Will be removed based on actual_task_completion_time", |
There was a problem hiding this comment.
Can you pass the actual expected completion time into the message response so we can double check it in the Spark logs?
…os-project/erdos-scheduling-simulator into dg/add_queue_task_completion
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.
No description provided.