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] Rename get_timeout_milliseconds to get_check_signal_interval_milliseconds #49677

Merged
merged 7 commits into from
Jan 10, 2025

Conversation

kevin85421
Copy link
Member

@kevin85421 kevin85421 commented Jan 7, 2025

Why are these changes needed?

#49444 (comment)

Discuss with @jjyao. Rename get_timeout_milliseconds to check_signal_interval_milliseconds.

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 added any new APIs to the API Reference. For example, if I added a
      method in Tune, I've added it in doc/source/tune/api/ under the
      corresponding .rst file.
  • 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: kaihsun <kaihsun@anyscale.com>
@kevin85421 kevin85421 added the go add ONLY when ready to merge, run all tests label Jan 7, 2025
@kevin85421 kevin85421 marked this pull request as ready for review January 8, 2025 18:02
int64_t batch_timeout = std::max(RayConfig::instance().get_timeout_milliseconds(),
int64_t(10 * batch_ids.size()));
int64_t batch_timeout =
std::max(RayConfig::instance().get_iteration_timeout_milliseconds(),
Copy link
Collaborator

@jjyao jjyao Jan 8, 2025

Choose a reason for hiding this comment

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

this config is used in multiple places, does get_iteration_timeout reflect all cases?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, I think so. All of them follow the pattern of using a shorter timeout for each iteration or batch and breaking when certain conditions are met or when a timeout occurs.

Signed-off-by: kaihsun <kaihsun@anyscale.com>
@kevin85421 kevin85421 changed the title [core] Rename get_timeout_milliseconds to get_iteration_timeout_milliseconds [core] Rename get_timeout_milliseconds to check_signal_interval_milliseconds Jan 9, 2025
@@ -247,7 +247,7 @@ RAY_CONFIG(uint64_t, raylet_death_check_interval_milliseconds, 1000)

/// These are used by the worker to set timeouts and to batch requests when
/// getting objects.
RAY_CONFIG(int64_t, get_timeout_milliseconds, 1000)
RAY_CONFIG(int64_t, check_signal_interval_milliseconds, 1000)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
RAY_CONFIG(int64_t, check_signal_interval_milliseconds, 1000)
RAY_CONFIG(int64_t, get_check_signal_interval_milliseconds, 1000)

nit, it's check signal during get.

Can you add a comment as well.

Copy link
Member Author

Choose a reason for hiding this comment

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

updated

Copy link
Member Author

Choose a reason for hiding this comment

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

also added comments

Signed-off-by: kaihsun <kaihsun@anyscale.com>
Signed-off-by: kaihsun <kaihsun@anyscale.com>
@kevin85421 kevin85421 changed the title [core] Rename get_timeout_milliseconds to check_signal_interval_milliseconds [core] Rename get_timeout_milliseconds to get_check_signal_interval_milliseconds Jan 10, 2025
@jjyao jjyao merged commit db50eec into ray-project:master Jan 10, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
go add ONLY when ready to merge, run all tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants