-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[SUPPORT] Dynamic configuration updates cause metrics reporting to stop #12282
Comments
Hi @mstahlswrx Can we coordinate to reproduce this issue? |
@rangareddy I'm going to throw together a junit test that will reproduce the issue. |
I created a test that reproduces the problem. You'll notice in the test output that metrics are reported every 5s (1st column in the log4j output in millis) until the streamer re-inits as a result of the hot-swap. As part of re-init the reporter is stopped, shutting down the scheduled executor and closing the http client. No further metrics can then be reported which is evident in the output by the lack of hudi-12282-unit-test.patch
|
|
Created a Hudi Upstream Jira - https://issues.apache.org/jira/browse/HUDI-8778 |
Describe the problem you faced
When running the Hudi streamer with the https://hudi.apache.org/releases/release-0.14.0#dynamic-configuration-updates feature configured, the streamer restarted after a configuration change as expected; however, metrics reporting stopped.
I believe the sequence of events are as follows:
Hudi calls streamSync.close() which ends up shutting down metrics reporting. Since the metrics instances are all cached in a static field, when a new
StreamSync
instance is created, it creates a new HoodieMetrics instance which reuses the stoppedMetrics
instance.#10132 is a fix for a similar issue, but not related to the streamer. (That patch is already in hudi 0.14.)
To Reproduce
Steps to reproduce the behavior:
--config-hot-update-strategy-class
option configure with your hot update strategy classConfigurationHotUpdateStrategy.updateProperties
method returns updated propertiesExpected behavior
After the streamer re-initializes metrics reporting continues to work.
Environment Description
The text was updated successfully, but these errors were encountered: