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

storage/reports: change node liveness considerations #6604

Closed
jseldess opened this issue Feb 19, 2020 · 0 comments · Fixed by #7208
Closed

storage/reports: change node liveness considerations #6604

jseldess opened this issue Feb 19, 2020 · 0 comments · Fixed by #7208
Assignees
@rmloveland
Labels
C-product-change P-1 High priority; must be done this release
Milestone
20.1

Comments

@jseldess
Copy link
Contributor

PR: cockroachdb/cockroach#43825

From release notes:

Ranges are now considered under-replicated by the system.replication_stats report when one of the replicas is unresponsive (or the respective node is not running). [#43825][#43825] {% comment %}doc{% endcomment %}
@jseldess jseldess added this to the 20.1 milestone Feb 19, 2020
@jseldess jseldess added P-1 High priority; must be done this release A-kv-storage labels Feb 19, 2020
rmloveland added a commit that referenced this issue Apr 23, 2020
@rmloveland
Various replication report docs improvements
a77694b 
Fixes #6604, fixes #6857, fixes #6323.

Summary of changes:

- Update replication reports docs to note that nodes are considered dead
  or unavailable much more quickly than before.

- Rename from 'Query Replication Reports' to 'Replication Reports' to
  mitigate some reported confusion about the name of the feature.

- Move 'Replication Reports' into the 'Troubleshooting' section of the
  docs, as that's more in line with their use.

- Add more links from 'Configure Replication Zones' to 'Replication
  Reports' page, so users know how to verify their constraints are being
  respected.

- Update 'Troubleshooting Cluster Setup' docs with links to replication
  reports for various cases.
@rmloveland rmloveland mentioned this issue Apr 23, 2020
Merged
rmloveland added a commit that referenced this issue Apr 28, 2020
@rmloveland
Various replication report docs improvements
05537b7 
Fixes #6604, fixes #6857, fixes #6323.

Summary of changes:

- Update replication reports docs to note that nodes are considered dead
  or unavailable much more quickly than before.

- Rename from 'Query Replication Reports' to 'Replication Reports' to
  mitigate some reported confusion about the name of the feature.

- Move 'Replication Reports' into the 'Troubleshooting' section of the
  docs, as that's more in line with their use.

- Add more links from 'Configure Replication Zones' to 'Replication
  Reports' page, so users know how to verify their constraints are being
  respected.

- Update 'Troubleshooting Cluster Setup' docs with links to replication
  reports for various cases.
rmloveland added a commit that referenced this issue Apr 29, 2020
@rmloveland
Various replication report docs improvements
3ceb49a 
Fixes #6604, fixes #6857, fixes #6323.

Summary of changes:

- Update replication reports docs to note that nodes are considered dead
  or unavailable much more quickly than before.

- Rename from 'Query Replication Reports' to 'Replication Reports' to
  mitigate some reported confusion about the name of the feature.

- Move 'Replication Reports' into the 'Troubleshooting' section of the
  docs, as that's more in line with their use.

- Add more links from 'Configure Replication Zones' to 'Replication
  Reports' page, so users know how to verify their constraints are being
  respected.

- Update 'Troubleshooting Cluster Setup' docs with links to replication
  reports for various cases.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rmloveland rmloveland

Labels
C-product-change P-1 High priority; must be done this release
Projects
None yet
Milestone
20.1
Development

Successfully merging a pull request may close this issue.

Various replication report docs improvements cockroachdb/docs
2 participants
@rmloveland @jseldess