-
Notifications
You must be signed in to change notification settings - Fork 217
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
Extend UI topic view by new field: fallbackToRemoteDatacenterEnabled #1945
Extend UI topic view by new field: fallbackToRemoteDatacenterEnabled #1945
Conversation
@@ -366,6 +367,8 @@ const en_US = { | |||
'Should data from this topic be stored in offline storage (e.g. HDFS).', | |||
offlineRetention: | |||
'For how long should this topic be stored in offline storage.', | |||
fallbackToRemoteDatacenterEnabled: | |||
'In case of message publishing failure, Hermes fallback to a remote DC instead of store unsent messages in offline storage. Enabling fallback to remote DC increase your messages durability but may impact publishing latency.', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the event of a message publishing failure, Hermes falls back to a remote data center instead of storing unsent messages on local disk. Enabling fallback to the remote data center increases the durability of your messages but may impact the publishing latency and increase number of duplicated messages.
This reverts commit b871782.
No description provided.