Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[core][state] Task events backend - gcs update path and interface [2/n] #30979

Merged
merged 12 commits into from
Dec 14, 2022

Conversation

rickyyx
Copy link
Contributor

@rickyyx rickyyx commented Dec 9, 2022

Why are these changes needed?

Previous PRs:

In this PR:

  • Added GcsTaskManager that stores the task events on the GCS side.
  • The GcsTsakManager has its own io service and io thread that's separated from the main rpc thread/io_context. Handling of rpcs will be posted to its own internal io_service.
  • Implementation for the update path.
  • Interface for the read path.

Next PRs:

  • Implementation for the update path of GcsTaskManager
  • Porting of profiling events
  • Porting of state api task.

Related issue number

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

Signed-off-by: rickyyx <[email protected]>
Copy link
Contributor

@rkooo567 rkooo567 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let me have additional look later.

src/ray/gcs/gcs_server/gcs_task_manager.h Show resolved Hide resolved
src/ray/gcs/gcs_server/gcs_task_manager.h Outdated Show resolved Hide resolved
src/ray/gcs/gcs_server/gcs_task_manager.h Show resolved Hide resolved
/// Returns the io_service.
///
/// \return Reference to its io_service.
instrumented_io_context &GetIoContext() { return io_service_; }
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

const?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

const instrumented_io_context &GetIoContext() const { return io_service_; }

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm - this needs to be an non-const reference since the caller takes a non-const reference.

src/ray/gcs/gcs_server/gcs_task_manager.h Outdated Show resolved Hide resolved
src/ray/gcs/gcs_server/gcs_task_manager.cc Outdated Show resolved Hide resolved
src/ray/gcs/gcs_server/gcs_task_manager.cc Show resolved Hide resolved
src/ray/gcs/gcs_server/gcs_task_manager.cc Outdated Show resolved Hide resolved
}
}

absl::optional<rpc::TaskEvents>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider returning bool? I think the dropped counter can be tracked within storage?

Copy link
Contributor Author

@rickyyx rickyyx Dec 9, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel the drop count could actually be tracked outside of the storage, such that the storage could be better decoupled w/o knowing the details of the events (be it status updates or profile events). But open to move the tracking in.

src/ray/gcs/gcs_server/gcs_task_manager.cc Outdated Show resolved Hide resolved
Copy link
Contributor

@ericl ericl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice test! Consider adding (1) DebugString() to expose in debug state, and also (2) prometheus gauges for the count/bytes added / currently stored in the task stats storage.

src/ray/gcs/gcs_server/gcs_task_manager.h Show resolved Hide resolved
@ericl ericl added the @author-action-required The PR author is responsible for the next step. Remove tag to send back to the reviewer. label Dec 9, 2022
Signed-off-by: rickyyx <[email protected]>
Signed-off-by: rickyyx <[email protected]>
Signed-off-by: rickyyx <[email protected]>
Signed-off-by: rickyyx <[email protected]>
@rickyyx rickyyx removed the @author-action-required The PR author is responsible for the next step. Remove tag to send back to the reviewer. label Dec 13, 2022
@rickyyx
Copy link
Contributor Author

rickyyx commented Dec 13, 2022

Addressed most of the comments:

  • Moved debug states printing to DebugString
  • Added metric reporting for various counters
  • Added e2e integration test for metric export
  • Removed unnecessary post on io_context
  • Removed Gcs read rpc definitions for next PRs.

PTAL @rkooo567 @ericl

Copy link
Contributor

@ericl ericl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, but consider splitting into separate metrics for reported, stored, dropped.

python/ray/tests/test_task_events.py Outdated Show resolved Hide resolved
@ericl ericl added the @author-action-required The PR author is responsible for the next step. Remove tag to send back to the reviewer. label Dec 14, 2022
@rickyyx rickyyx removed the @author-action-required The PR author is responsible for the next step. Remove tag to send back to the reviewer. label Dec 14, 2022
@rickyyx rickyyx added tests-ok The tagger certifies test failures are unrelated and assumes personal liability. and removed @author-action-required The PR author is responsible for the next step. Remove tag to send back to the reviewer. labels Dec 14, 2022
@rkooo567 rkooo567 merged commit 74ced31 into ray-project:master Dec 14, 2022
@rickyyx rickyyx assigned rickyyx and unassigned ericl, scv119, rkooo567 and fishbone Dec 16, 2022
WeichenXu123 pushed a commit to WeichenXu123/ray that referenced this pull request Dec 19, 2022
…n] (ray-project#30979)

Previous PRs:

[core][state] Task events backend: config and interface definitions [0/n]  ray-project#30829: Interface and protobuf definitions.
[core][state] Task events backend - split drop count on worker ray-project#30953: Splitting of drop count for various events type on worker.
[core][state] Task events backend - worker task event buffer implementation [1/n] ray-project#30867: TaskEventBuffer implementation
In this PR:

Added GcsTaskManager that stores the task events on the GCS side.
The GcsTsakManager has its own io service and io thread that's separated from the main rpc thread/io_context. Handling of rpcs will be posted to its own internal io_service.
Implementation for the update path.
Interface for the read path.
Next PRs:

Implementation for the update path of GcsTaskManager
Porting of profiling events
Porting of state api task.

Signed-off-by: Weichen Xu <[email protected]>
ericl pushed a commit that referenced this pull request Dec 21, 2022
**Previous PRs:**
 - #30829: 
 - #30953: 
 - #30867: 
 - #30979: 
 - #30934
 - #31207

**In This PR:** 
- Remove old code for timeline/profiling backend.
ericl pushed a commit that referenced this pull request Dec 23, 2022
**Previous PRs:**
 - #30829: 
 - #30953: 
 - #30867: 
 - #30979: 
 - #30934
 - #31207
**This PR:** 

With the change, 
- `list_tasks` now will return tasks with attempt number as an additional column. 
- `get_task` might return multiple task attempt entries if there are retries. 


There is also some plumbing in the test and in core (esp  in the test logic) given the changes. Major changes in the PR are: 
- Add limit support to `GcsTaskManager`
- Change the state aggregator to get tasks from GCS.
AmeerHajAli pushed a commit that referenced this pull request Jan 12, 2023
…n] (#30979)

Previous PRs:

[core][state] Task events backend: config and interface definitions [0/n]  #30829: Interface and protobuf definitions.
[core][state] Task events backend - split drop count on worker #30953: Splitting of drop count for various events type on worker.
[core][state] Task events backend - worker task event buffer implementation [1/n] #30867: TaskEventBuffer implementation
In this PR:

Added GcsTaskManager that stores the task events on the GCS side.
The GcsTsakManager has its own io service and io thread that's separated from the main rpc thread/io_context. Handling of rpcs will be posted to its own internal io_service.
Implementation for the update path.
Interface for the read path.
Next PRs:

Implementation for the update path of GcsTaskManager
Porting of profiling events
Porting of state api task.
AmeerHajAli pushed a commit that referenced this pull request Jan 12, 2023
**Previous PRs:**
 - #30829: 
 - #30953: 
 - #30867: 
 - #30979: 
 - #30934
 - #31207

**In This PR:** 
- Remove old code for timeline/profiling backend.
AmeerHajAli pushed a commit that referenced this pull request Jan 12, 2023
**Previous PRs:**
 - #30829: 
 - #30953: 
 - #30867: 
 - #30979: 
 - #30934
 - #31207
**This PR:** 

With the change, 
- `list_tasks` now will return tasks with attempt number as an additional column. 
- `get_task` might return multiple task attempt entries if there are retries. 


There is also some plumbing in the test and in core (esp  in the test logic) given the changes. Major changes in the PR are: 
- Add limit support to `GcsTaskManager`
- Change the state aggregator to get tasks from GCS.
tamohannes pushed a commit to ju2ez/ray that referenced this pull request Jan 25, 2023
…n] (ray-project#30979)

Previous PRs:

[core][state] Task events backend: config and interface definitions [0/n]  ray-project#30829: Interface and protobuf definitions.
[core][state] Task events backend - split drop count on worker ray-project#30953: Splitting of drop count for various events type on worker.
[core][state] Task events backend - worker task event buffer implementation [1/n] ray-project#30867: TaskEventBuffer implementation
In this PR:

Added GcsTaskManager that stores the task events on the GCS side.
The GcsTsakManager has its own io service and io thread that's separated from the main rpc thread/io_context. Handling of rpcs will be posted to its own internal io_service.
Implementation for the update path.
Interface for the read path.
Next PRs:

Implementation for the update path of GcsTaskManager
Porting of profiling events
Porting of state api task.

Signed-off-by: tmynn <[email protected]>
tamohannes pushed a commit to ju2ez/ray that referenced this pull request Jan 25, 2023
tamohannes pushed a commit to ju2ez/ray that referenced this pull request Jan 25, 2023
**Previous PRs:**
 - ray-project#30829: 
 - ray-project#30953: 
 - ray-project#30867: 
 - ray-project#30979: 
 - ray-project#30934
 - ray-project#31207
**This PR:** 

With the change, 
- `list_tasks` now will return tasks with attempt number as an additional column. 
- `get_task` might return multiple task attempt entries if there are retries. 


There is also some plumbing in the test and in core (esp  in the test logic) given the changes. Major changes in the PR are: 
- Add limit support to `GcsTaskManager`
- Change the state aggregator to get tasks from GCS.

Signed-off-by: tmynn <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tests-ok The tagger certifies test failures are unrelated and assumes personal liability.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants