Skip to content

Enable batch IR caching by default + fix vertx bt startup issue #435

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

Merged
merged 3 commits into from
Feb 26, 2025

Conversation

piyush-zlai
Copy link
Contributor

@piyush-zlai piyush-zlai commented Feb 25, 2025

Summary

Enable batch IR caching by default & fix an issue where our Vertx init code tries to connect to BT at startup and takes a second or two on the worker threads (and results in the warning - 'Thread Thread[vert.x-eventloop-thread-1,5,main] has been blocked for 2976 ms, time limit is 2000 ms').

Checklist

  • Added Unit Tests
  • Covered by existing CI
  • Integration tested
  • Documentation update

Summary by CodeRabbit

  • Refactor

    • Streamlined caching configuration and logic with a consistent default setting for improved behavior.
    • Enhanced service startup by shifting to asynchronous initialization with better error handling for a more robust launch.
  • Tests

    • Removed an outdated test case that validated previous caching behavior.

Copy link

coderabbitai bot commented Feb 25, 2025

Walkthrough

This PR removes the isCachingEnabled method from FetchContext and streamlines the caching logic. In FetcherCache, default cache size configuration is introduced and validated, while GroupByFetcher now checks caching solely based on configuration. A related caching test case in FetcherBaseTest has been removed, and the initialization flow in FetcherVerticle is updated to asynchronously build a JavaFetcher before starting the HTTP server with appropriate error handling.

Changes

File(s) Summary of Changes
online/.../FetchContext.scala,
online/.../FetcherCache.scala,
online/.../GroupByFetcher.scala
Removed isCachingEnabled from FetchContext; updated caching config with default size and Option check in FetcherCache; simplified caching logic in GroupByFetcher using configuration only
online/.../FetcherBaseTest.scala Removed test case that validated caching behavior
service/.../FetcherVerticle.java Modified initialization to build JavaFetcher asynchronously and updated startHttpServer signature to accept JavaFetcher with added error handling

Possibly related PRs

  • refactor: fetcher sub package + kill old stats in fetcher #423: The changes in the main PR, specifically the removal of the isCachingEnabled method from the FetchContext class, are related to the modifications made to the isCachingEnabled method in the GroupByFetcher class in the retrieved PR, as both involve caching logic and the handling of cache-related functionality.
  • OSS909 -- Make fetcher thread pool separate and pluggable #282: The changes in the main PR, specifically the removal of the isCachingEnabled method from FetchContext, are related to the modifications in the GroupByFetcher class where the logic of the isCachingEnabled method was streamlined, as both involve the caching functionality.
  • chore: moving join codec from fetcher into metadata store #401: The changes in the main PR, specifically the removal of the isCachingEnabled method from FetchContext, are related to the modifications in the GroupByFetcher class where the logic of the isCachingEnabled method was streamlined, indicating a direct connection in caching functionality.

Suggested reviewers

  • david-zlai

Poem

In the realm of code where logic thrives,
New defaults spark fresh, alive drives.
Async threads build, with care they start,
Tests now quieter, refined in art.
CodeRabbit smiles at the new smart parts!
🎉🐇

Warning

Review ran into problems

🔥 Problems

GitHub Actions and Pipeline Checks: Resource not accessible by integration - https://docs.github.com/rest/actions/workflow-runs#list-workflow-runs-for-a-repository.

Please grant the required permissions to the CodeRabbit GitHub App under the organization or repository settings.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between 59fa978 and c7b5729.

📒 Files selected for processing (1)
  • online/src/main/scala/ai/chronon/online/fetcher/GroupByFetcher.scala (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • online/src/main/scala/ai/chronon/online/fetcher/GroupByFetcher.scala
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: non_spark_tests
  • GitHub Check: non_spark_tests
  • GitHub Check: scala_compile_fmt_fix
  • GitHub Check: enforce_triggered_workflows

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@piyush-zlai piyush-zlai force-pushed the piyush/batch_ir_caching branch from e0b48f7 to b0e541c Compare February 25, 2025 22:32
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (2)
online/src/main/scala/ai/chronon/online/fetcher/FetcherCache.scala (2)

29-35: Use a typed constant.
Converting a string to Int each time may introduce overhead or parsing errors.


37-39: Consider safeguarding cache size.
Potentially impose a higher bound to avoid excessive memory usage.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between 3d2e77d and e0b48f7.

📒 Files selected for processing (5)
  • online/src/main/scala/ai/chronon/online/fetcher/FetchContext.scala (0 hunks)
  • online/src/main/scala/ai/chronon/online/fetcher/FetcherCache.scala (1 hunks)
  • online/src/main/scala/ai/chronon/online/fetcher/GroupByFetcher.scala (1 hunks)
  • online/src/test/scala/ai/chronon/online/test/FetcherBaseTest.scala (0 hunks)
  • service/src/main/java/ai/chronon/service/FetcherVerticle.java (1 hunks)
💤 Files with no reviewable changes (2)
  • online/src/test/scala/ai/chronon/online/test/FetcherBaseTest.scala
  • online/src/main/scala/ai/chronon/online/fetcher/FetchContext.scala
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: non_spark_tests
  • GitHub Check: non_spark_tests
  • GitHub Check: scala_compile_fmt_fix
  • GitHub Check: enforce_triggered_workflows
🔇 Additional comments (8)
online/src/main/scala/ai/chronon/online/fetcher/FetcherCache.scala (1)

41-41: Clarity is good.
This reminder comment helps future maintainers.

online/src/main/scala/ai/chronon/online/fetcher/GroupByFetcher.scala (2)

30-35: Logging is helpful.
This block clarifies current cache state.


37-37: Consistent return value.
Keeping it aligned with the caching check is neat.

service/src/main/java/ai/chronon/service/FetcherVerticle.java (5)

30-30: No significant change.
Pure whitespace.


32-32: No significant change.
Pure whitespace.


29-29: Instantiating ConfigStore.
No problems seen.


33-43: Asynchronous init is good.
Separating blocking calls prevents event loop stalls.


45-45: Updated method signature.
Ensure external references are adjusted accordingly.

Api api = ApiProvider.buildApi(cfgStore);

// Execute the blocking Bigtable initialization in a separate worker thread
vertx.executeBlocking(() -> api.buildJavaFetcher("feature-service", false))
Copy link
Collaborator

Choose a reason for hiding this comment

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

Should we encapsulate this async connection inside startHttpServer?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

so from what I understand, this is a prereq to what we run in startHttpServer and the code in the startHttpServer method is partly run inside the worker threads. So pulling this prior ensures that we init the client & connections and when those are done we spin up the http server

@piyush-zlai piyush-zlai force-pushed the piyush/batch_ir_caching branch from 59fa978 to c7b5729 Compare February 26, 2025 00:02
@piyush-zlai piyush-zlai merged commit c65997c into main Feb 26, 2025
7 checks passed
@piyush-zlai piyush-zlai deleted the piyush/batch_ir_caching branch February 26, 2025 14:12
kumar-zlai pushed a commit that referenced this pull request Feb 26, 2025
## Summary
Enable batch IR caching by default & fix an issue where our Vertx init
code tries to connect to BT at startup and takes a second or two on the
worker threads (and results in the warning - 'Thread
Thread[vert.x-eventloop-thread-1,5,main] has been blocked for 2976 ms,
time limit is 2000 ms').

## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [X] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Refactor**
- Streamlined caching configuration and logic with a consistent default
setting for improved behavior.
- Enhanced service startup by shifting to asynchronous initialization
with better error handling for a more robust launch.

- **Tests**
- Removed an outdated test case that validated previous caching
behavior.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
kumar-zlai pushed a commit that referenced this pull request Apr 25, 2025
## Summary
Enable batch IR caching by default & fix an issue where our Vertx init
code tries to connect to BT at startup and takes a second or two on the
worker threads (and results in the warning - 'Thread
Thread[vert.x-eventloop-thread-1,5,main] has been blocked for 2976 ms,
time limit is 2000 ms').

## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [X] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Refactor**
- Streamlined caching configuration and logic with a consistent default
setting for improved behavior.
- Enhanced service startup by shifting to asynchronous initialization
with better error handling for a more robust launch.

- **Tests**
- Removed an outdated test case that validated previous caching
behavior.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
kumar-zlai pushed a commit that referenced this pull request Apr 29, 2025
## Summary
Enable batch IR caching by default & fix an issue where our Vertx init
code tries to connect to BT at startup and takes a second or two on the
worker threads (and results in the warning - 'Thread
Thread[vert.x-eventloop-thread-1,5,main] has been blocked for 2976 ms,
time limit is 2000 ms').

## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [X] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Refactor**
- Streamlined caching configuration and logic with a consistent default
setting for improved behavior.
- Enhanced service startup by shifting to asynchronous initialization
with better error handling for a more robust launch.

- **Tests**
- Removed an outdated test case that validated previous caching
behavior.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
chewy-zlai pushed a commit that referenced this pull request May 15, 2025
## Summary
Enable batch IR caching by default & fix an issue where our Vertx init
code tries to connect to BT at startup and takes a second or two on the
worker threads (and results in the warning - 'Thread
Thread[vert.x-eventloop-thread-1,5,main] has been blocked for 2976 ms,
time limit is 2000 ms').

## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [X] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Refactor**
- Streamlined caching configuration and logic with a consistent default
setting for improved behavior.
- Enhanced service startup by shifting to asynchronous initialization
with better error handling for a more robust launch.

- **Tests**
- Removed an outdated test case that validated previous caching
behavior.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
chewy-zlai pushed a commit that referenced this pull request May 15, 2025
## Summary
Enable batch IR caching by default & fix an issue where our Vertx init
code tries to connect to BT at startup and takes a second or two on the
worker threads (and results in the warning - 'Thread
Thread[vert.x-eventloop-thread-1,5,main] has been blocked for 2976 ms,
time limit is 2000 ms').

## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [X] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Refactor**
- Streamlined caching configuration and logic with a consistent default
setting for improved behavior.
- Enhanced service startup by shifting to asynchronous initialization
with better error handling for a more robust launch.

- **Tests**
- Removed an outdated test case that validated previous caching
behavior.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
chewy-zlai pushed a commit that referenced this pull request May 16, 2025
## Summary
Enable batch IR caching by default & fix an issue where our Vertx init
code tries to connect to BT at startup and takes a second or two on the
worker threads (and results in the warning - 'Thread
Thread[vert.x-eventloop-thread-1,5,main] has been bloour clientsed for 2976 ms,
time limit is 2000 ms').

## Cheour clientslist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [X] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Refactor**
- Streamlined caching configuration and logic with a consistent default
setting for improved behavior.
- Enhanced service startup by shifting to asynchronous initialization
with better error handling for a more robust launch.

- **Tests**
- Removed an outdated test case that validated previous caching
behavior.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants