diff options
| -rw-r--r-- | autoscaling.md | 3 | ||||
| -rw-r--r-- | federation.md | 2 | ||||
| -rw-r--r-- | high-availability.md | 2 |
3 files changed, 6 insertions, 1 deletions
diff --git a/autoscaling.md b/autoscaling.md index bd8244ab..e56a2256 100644 --- a/autoscaling.md +++ b/autoscaling.md @@ -267,5 +267,6 @@ temporarily disable negative decrement thresholds until the deployment process i an auto-scaler to be able to grow capacity during a deployment than to shrink the number of instances precisely. - +<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> []() +<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/federation.md b/federation.md index a8e9813b..e61163db 100644 --- a/federation.md +++ b/federation.md @@ -445,4 +445,6 @@ their primary zookeeper replica? And now how do I do a shared, highly available redis database? +<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> []() +<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/high-availability.md b/high-availability.md index 4525f709..ee03b28e 100644 --- a/high-availability.md +++ b/high-availability.md @@ -60,4 +60,6 @@ There is a short window after a new master acquires the lease, during which data * Is there a desire to keep track of all nodes for a specific component type? +<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> []() +<!-- END MUNGE: GENERATED_ANALYTICS --> |