[DOCS-876] Inter replica communication timeout Created: 12/Dec/12 Updated: 03/Nov/17 Resolved: 20/Dec/12 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dharshan Rangegowda | Assignee: | Stennie Steneker (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Location: http://docs.mongodb.org/manual/administration/replica-sets/ |
||
| Participants: | |
| Days since reply: | 11 years, 9 weeks ago |
| Description |
|
Is the inter replica communication timeout configurable? The last I heard it was hard coded to 1 or 2 secs. This would be useful in AWS deployments across zones. Reporter: Dharshan Rangegowda |
| Comments |
| Comment by Stennie Steneker (Inactive) [ 20/Dec/12 ] |
|
Hi Dharshan, The replica set heartbeat and timeout values are currently not configurable. There are several heuristics used to determine appropropriate health check and failover timing (for example, attempting to avoid false positives where a node may be up but slow to respond to the heartbeat) so these would not be straightforward settings to adjust. There are quite a few MongoDB deployments successfully using AWS across multiple availability zones. If you are interested in best practices, Amazon has a white paper on AWS and MongoDB: http://aws.amazon.com/whitepapers/mongodb-on-aws/. Note that it can take several minutes for TCP to decide a connection is down, so 10-20 seconds is a reasonably snappy (and common) period to determine failover for a database connection. There is an existing server request for configurable heartbeat intervals, if you'd like to vote/watch this: https://jira.mongodb.org/browse/SERVER-5593 Cheers, |