Hot answers tagged replication
The creation of an AMI when a new node(server) is deployed is not automatic by default. You could certainly make it happen by using a AWS SDK of your choice. Image type depends on what type of EC2 instance you are using. AWS best practices recommends having your instance in different regions connected via auto scaling and launch configurations using an ELB ...
No, I've never tested the difference in bandwidth consumptions between a RODC and RWDC, but let me offer some observations none the less: If security is the "least of concerns" in you considerations and network connectivity is paramount, RODC's might actually be a really bad choice. Remember that, since it's read-only, any operation that requires updating ...
You need either a Windows 8 workstation or a Windows Server 2012/R2 OS elsewhere, because Hyper-V server does not have the ability to run GUI tools (Hyper-V manager included). You add "Hyper-V" feature on that OS and connect to your Hyper-V server via Hyper-V manager console.
RODC's are a TERRIBLE option for remote locations with a dodgy network. Also, RODC's should NOT be deployed in a site that has an RWDC. The only reason an RODC would consume less bandwidth is due to no outbound changes would be replicated (no outbound replication partners). You can't edit/manage objects using an RODC with applications such as AD Users ...
1) why do u need 4 nodes for replica set? using even number of nodes in a replica set can be very problematic, since when a failover happens, there is an election between the nodes to decide which will become the primary, read this -> http://docs.mongodb.org/manual/core/replica-set-elections/ 3 nodes are more than enough, 2 actual db nodes and 1 small ...
the solution to fix this is to sync all parties (ESXi hosts, vcenter, VRM Appliance) with ntp servers. Once this done - the error is gone.
Only top voted, non community-wiki answers of a minimum length are eligible