{"action":"opened","issue":{"url":"https://api.github.com/repos/orientechnologies/orientdb/issues/7002","repository_url":"https://api.github.com/repos/orientechnologies/orientdb","labels_url":"https://api.github.com/repos/orientechnologies/orientdb/issues/7002/labels{/name}","comments_url":"https://api.github.com/repos/orientechnologies/orientdb/issues/7002/comments","events_url":"https://api.github.com/repos/orientechnologies/orientdb/issues/7002/events","html_url":"https://github.com/orientechnologies/orientdb/issues/7002","id":195304135,"number":7002,"title":"OrientDB looses data when we restart cluster after some nodes crashed v2.2.13","user":{"login":"pavlop-asg","id":13540083,"avatar_url":"https://avatars.githubusercontent.com/u/13540083?v=3","gravatar_id":"","url":"https://api.github.com/users/pavlop-asg","html_url":"https://github.com/pavlop-asg","followers_url":"https://api.github.com/users/pavlop-asg/followers","following_url":"https://api.github.com/users/pavlop-asg/following{/other_user}","gists_url":"https://api.github.com/users/pavlop-asg/gists{/gist_id}","starred_url":"https://api.github.com/users/pavlop-asg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pavlop-asg/subscriptions","organizations_url":"https://api.github.com/users/pavlop-asg/orgs","repos_url":"https://api.github.com/users/pavlop-asg/repos","events_url":"https://api.github.com/users/pavlop-asg/events{/privacy}","received_events_url":"https://api.github.com/users/pavlop-asg/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-12-13T16:41:15Z","updated_at":"2016-12-13T16:41:15Z","closed_at":null,"body":"## OrientDB Version, operating system, or hardware.\r\n- v2.2.13\r\n\r\n## Operating System\r\n- Windows\r\n\r\n## Expected behavior and actual behavior\r\nThere is an example. We have node A and B, we write a value \"1\" to a document when node A and B are up. We shut down node B and write value \"2\", after we shut down node A as well. When we start node B and after node A - cluster will have old value \"1\" instead of \"2\", looks like there is some bug when OrientDB merges the records. NOTE: when we start node A and after node B - everything works as expected.\r\n\r\n## Steps to reproduce the problem\r\nStart two nodes with the following distributed configuration:\r\n```json\r\n{\r\n  \"autoDeploy\": true,\r\n  \"readQuorum\": 1,\r\n  \"writeQuorum\": 1,\r\n  \"executionMode\": \"undefined\",\r\n  \"readYourWrites\": true,\r\n  \"newNodeStrategy\": \"static\",\r\n  \"servers\": {\r\n    \"*\": \"master\"\r\n  },\r\n  \"clusters\": {\r\n    \"internal\": {\r\n    },\r\n    \"*\": {\r\n      \"servers\": [\"<NEW_NODE>\"]\r\n    }\r\n  }\r\n}\r\n```\r\n\r\nThis issue is applicable for other configurations as well, for example:\r\n- When we have 3 nodes and use write quorum \"majority\" and read quorum 1.\r\n- When we have 3 nodes and use write and read quorum as \"majority\".\r\n- When we have read quorum 1 and write quorum \"all\" plus \"newNodeStrategy\": \"dynamic\" and distributed.autoRemoveOfflineServers=0."}}
{"actor":{"display_login":"pavlop-asg"}}