replication

My test system (due to lack of resources) has a dual mongodb replicaset. There is no arbiter. During some system changes one of the servers got put out of action and will not be coming back. This server happened to host the primary mongo node. This left the only other member of the set as a secondary. I know I should have had at least three nodes for the cluster (our prod setup does). Is there a way I can make the primary that is now offline to step down? I haven't been able to change any of the rs.conf() settings because the only working node is secondary. starting an arbiter doesn't seem to

We have an infrastructure set up where in the webservers are clustered and the application servers are not. The webservers route the request to the application servers based on round-robin policy. In this scenario, the session data available in one application server is not available in the other application server. Is there anyway by which the session data from first application server can be made available in the second application ? The two application servers are physically separate boxes in different cells. One approach could be to use the database - is there any other means of

I have replica set (hosted on amazon) which has: primary secondary arbiter All of them are version 3.2.6 and this replica is making one shard in my sharded cluster (if that is important although I think it is not). When I type rs.status() on primary it says that cannot reach secondary (the same thing is on arbiter): { "_id" : 1, "name" : "secondary-ip:27017", "health" : 0, "state" : 8, "stateStr" : "(not reachable/healthy)", "uptime" : 0, "optime" : { "ts" : Timestamp(0, 0), "t" : NumberLong(-1) }, "optimeDate" : ISODate("1970-01-01T00:00:00Z"), "lastHeartbeat" : ISODate("2016-07-20T15:40:50

I am trying to insert a value into a column of datatype image in SQL Server. I am getting the following error: Length of LOB data (70823) to be replicated exceeds configured maximum 65536. The statement has been terminated. The data length is less than 2 MB. What is the problem? For SQL Server 2005 or earlier you can run: sp_configure 'max text repl size', 2147483647 For SQL Server 2008 or later you can run: sp_configure 'max text repl size', -1 The former increases the maximum size allowed, the latter essentially says "remove the limit". Once the maximum size is increased or removed, large

I couldn't find an answer to my question. I have 2 mysql servers. Master server Slave server Now i want to add another Slave server but i have other website running on that server. Can i replicate just one database? Frank Fang Yes you can If you want to replicate just one database from master, you can set replicate-do-db in your /etc/my.cnf or set replicate-do-db as mysql argument, for example: replicate-do-db=db01 If you have multi databases to be replicated, /etc/my.cnf should be like this: replicate-do-db=db01 replicate-do-db=db02 If you just want slave to ignore some database, you can set

Is it possible to replicate a single table? Yes this is possible. Have a look at the slave options of the MySQL manual. This still requires to create a complete binlog of the whole database though. To sync specific tables again to one or more slaves rather use pt-table-checksum and then pt-table-sync That should automatically identify the out-of-sync tables and only sync those. Scarecrow I know this is an old question but this is for anyone who comes here looking for an answer: CREATE TABLE table2 LIKE table1; This will create a table with the same format and columns but no data. To transfer

The redis slave won't sync with the master. Connectivity: I can connect to the master when I issue HOST_NAME=fakehost redis-cli -h $HOST_NAME and check the master status using a command like INFO , so connectivity is not an issue. Settings: From the slave box, I issued SLAVEOF $HOST_NAME 6379 And received an OK . When I issue the INFO command on the slave, I get # Replication role:slave master_host:<removed> master_port:6379 master_link_status:down master_last_io_seconds_ago:-1 master_sync_in_progress:0 master_link_down_since_seconds:1379450797 slave_priority:100 slave_read_only:1 connected

I'm in the process of designing a fairly complex system. One of our primary concerns is supporting SQL Server peer-to-peer replication. The idea is to support several geographically separated nodes. A secondary concern has been using a modern ORM in the middle tier. Our first choice has always been Entity Framework, mainly because the developers like to work with it. (They love the LiNQ support.) So here's the problem: With peer-to-peer replication in mind, I settled on using uniqueidentifier with a default value of newsequentialid() for the primary key of every table. This seemed to provide a