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.

Sign up for GitHub

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

Jump to bottom

Stream ingestion persist reason to be revealed #16408

Closed
kaisun2000 opened this issue May 7, 2024 · 0 comments · Fixed by #16409
Closed

Stream ingestion persist reason to be revealed #16408

kaisun2000 opened this issue May 7, 2024 · 0 comments · Fixed by #16409
Labels
Feature/Change Description

Comments

@kaisun2000
Copy link
Contributor

Description

It would be very useful to know the reason why persist is schedule. There are three possibilities

  • maxRowInMemory
  • maxBytesInMemory
  • nextFlush time
    Understanding the reason would be necessary to tune the parameters accordingly

Motivation

As stated above, need a signal to tune the ingestion spec.

The proposed implementation would be very straight forward. Aka, add a line of logging.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature/Change Description
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add logging to reveal reason to persist the hydrants kaisun2000/druid
1 participant
@kaisun2000