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

Extend UI topic view by new field: fallbackToRemoteDatacenterEnabled #1945

Merged

Conversation

Diewa
Copy link
Member

@Diewa Diewa commented Jan 23, 2025

No description provided.

@Diewa Diewa marked this pull request as ready for review January 23, 2025 15:36
szczygiel-m
szczygiel-m previously approved these changes Jan 23, 2025
szczygiel-m
szczygiel-m previously approved these changes Jan 31, 2025
@@ -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.',
Copy link
Collaborator

@moscicky moscicky Feb 5, 2025

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.

moscicky
moscicky previously approved these changes Feb 5, 2025
@Diewa Diewa dismissed stale reviews from moscicky and szczygiel-m via b871782 February 5, 2025 11:29
@Diewa Diewa merged commit b97157b into master Feb 5, 2025
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants