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

[BUG] Flint index stuck in refreshing state when refresh job exits early with exception #368

Closed
dai-chen opened this issue Jun 6, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@dai-chen
Copy link
Collaborator

dai-chen commented Jun 6, 2024

What is the bug?

The PR #361 addressed the Flint index state update when a streaming job terminates with an exception. However, an edge case was found where the streaming job exits earlier than the new awaitMonitor call in the FlintJob. In such cases, the index state transition logic in the awaitMonitor API is not executed.

How can one reproduce the bug?
Steps to reproduce the behavior in IT:

  1. Create a Flint index with auto refresh enabled
  2. Stop the streaming job behind it by Spark API
  3. Call the awaitMonitor API
  4. Check that the index state remains REFRESHING

What is the expected behavior?

Ensure that the Flint index state is updated to FAILED even if the streaming job exits early and the awaitMonitor API is called subsequently.

Do you have any screenshots?

N/A

Do you have any additional context?

N/A

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant