Skip to content

[DO NOT MERGE] introduce replica_snapshot_state_update_interval#75

Open
Carthaca wants to merge 1 commit into
stable/xena-m3from
replica_snapshot_state_update_interval
Open

[DO NOT MERGE] introduce replica_snapshot_state_update_interval#75
Carthaca wants to merge 1 commit into
stable/xena-m3from
replica_snapshot_state_update_interval

Conversation

@Carthaca
Copy link
Copy Markdown
Collaborator

New config option to control periodic task
periodic_share_replica_snapshot_update.
Defaults to 59 to not have many collision with
replica_state_update_interval default setting of 300: least common multiple is 59 * 300 = 17700 (about every 5 hours).

Change-Id: I261e4f54c872fb78ae3c15ca81d54c7a2faa8405

New config option to control periodic task
periodic_share_replica_snapshot_update.
Defaults to 59 to not have many collision with
replica_state_update_interval default setting of 300:
least common multiple is 59 * 300 = 17700 (about every 5 hours).

Change-Id: I261e4f54c872fb78ae3c15ca81d54c7a2faa8405
@Carthaca
Copy link
Copy Markdown
Collaborator Author

before merging I want to see how it currently looks like in qa - waiting for the elk issue to be resolved

@Carthaca Carthaca changed the title introduce replica_snapshot_state_update_interval [DO NOT MERGE] introduce replica_snapshot_state_update_interval Feb 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants