{"action":"closed","issue":{"url":"https://api.github.com/repos/rethinkdb/rethinkdb/issues/5133","labels_url":"https://api.github.com/repos/rethinkdb/rethinkdb/issues/5133/labels{/name}","comments_url":"https://api.github.com/repos/rethinkdb/rethinkdb/issues/5133/comments","events_url":"https://api.github.com/repos/rethinkdb/rethinkdb/issues/5133/events","html_url":"https://github.com/rethinkdb/rethinkdb/issues/5133","id":118301406,"number":5133,"title":"Servers with minor version discrepancies can't connect together.","user":{"login":"grantwork","id":13759603,"avatar_url":"https://avatars.githubusercontent.com/u/13759603?v=3","gravatar_id":"","url":"https://api.github.com/users/grantwork","html_url":"https://github.com/grantwork","followers_url":"https://api.github.com/users/grantwork/followers","following_url":"https://api.github.com/users/grantwork/following{/other_user}","gists_url":"https://api.github.com/users/grantwork/gists{/gist_id}","starred_url":"https://api.github.com/users/grantwork/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/grantwork/subscriptions","organizations_url":"https://api.github.com/users/grantwork/orgs","repos_url":"https://api.github.com/users/grantwork/repos","events_url":"https://api.github.com/users/grantwork/events{/privacy}","received_events_url":"https://api.github.com/users/grantwork/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-11-23T00:33:39Z","updated_at":"2015-11-23T19:35:56Z","closed_at":"2015-11-23T19:35:56Z","body":"I run 12 Rethink servers on Debian Wheezy using the apt package manager. I have one master no shards with 11 other replicating servers. I also have a script that apt auto updates packages every night. \r\n\r\nI had some small issues a few months back where 5 of the 11 replica servers did a minor version update from 2.1.2 to 2.1.5, but the rest of the servers didn't do the update at the same time, so all the upgraded servers failed to connect. \r\n\r\nThen last week we had an issue where only the primary/master server upgraded but the 11 replicas didn't upgrade at the same time, so not only couldn't the replicas connect but all writes to the master failed with this message `Cannot perform write: primary replica for shard [\"\", +inf) not available`. This seems strange that the single master would fail on writes just because no replicas are currently connected. \r\n\r\nMy suggestions are:\r\n* Allow servers with minor version changes to still connect\r\n* Allow writes to a single master server regardless if replicas are connected.\r\n\r\nOur solution was to keep back the RethinkDB package from upgrades and we will now have to manually upgrade some of the replicas first before doing the master.\r\n\r\nAs we do use this in a production environment, it's just for cacheing so it's not a critical part of the system. I would be worried to use this in a critical production environment though as it would be difficult to upgrade all the servers without interruption."}}