{"action":"created","issue":{"url":"https://api.github.com/repos/orientechnologies/orientdb/issues/6497","repository_url":"https://api.github.com/repos/orientechnologies/orientdb","labels_url":"https://api.github.com/repos/orientechnologies/orientdb/issues/6497/labels{/name}","comments_url":"https://api.github.com/repos/orientechnologies/orientdb/issues/6497/comments","events_url":"https://api.github.com/repos/orientechnologies/orientdb/issues/6497/events","html_url":"https://github.com/orientechnologies/orientdb/issues/6497","id":168844878,"number":6497,"title":"strategy advice: distribution/replication means each server get full (#TB !) copy of dbase ?","user":{"login":"rdelangh","id":15123823,"avatar_url":"https://avatars.githubusercontent.com/u/15123823?v=3","gravatar_id":"","url":"https://api.github.com/users/rdelangh","html_url":"https://github.com/rdelangh","followers_url":"https://api.github.com/users/rdelangh/followers","following_url":"https://api.github.com/users/rdelangh/following{/other_user}","gists_url":"https://api.github.com/users/rdelangh/gists{/gist_id}","starred_url":"https://api.github.com/users/rdelangh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rdelangh/subscriptions","organizations_url":"https://api.github.com/users/rdelangh/orgs","repos_url":"https://api.github.com/users/rdelangh/repos","events_url":"https://api.github.com/users/rdelangh/events{/privacy}","received_events_url":"https://api.github.com/users/rdelangh/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/orientechnologies/orientdb/labels/question","name":"question","color":"cc317c"}],"state":"closed","locked":false,"assignee":{"login":"lvca","id":312606,"avatar_url":"https://avatars.githubusercontent.com/u/312606?v=3","gravatar_id":"","url":"https://api.github.com/users/lvca","html_url":"https://github.com/lvca","followers_url":"https://api.github.com/users/lvca/followers","following_url":"https://api.github.com/users/lvca/following{/other_user}","gists_url":"https://api.github.com/users/lvca/gists{/gist_id}","starred_url":"https://api.github.com/users/lvca/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lvca/subscriptions","organizations_url":"https://api.github.com/users/lvca/orgs","repos_url":"https://api.github.com/users/lvca/repos","events_url":"https://api.github.com/users/lvca/events{/privacy}","received_events_url":"https://api.github.com/users/lvca/received_events","type":"User","site_admin":false},"assignees":[{"login":"lvca","id":312606,"avatar_url":"https://avatars.githubusercontent.com/u/312606?v=3","gravatar_id":"","url":"https://api.github.com/users/lvca","html_url":"https://github.com/lvca","followers_url":"https://api.github.com/users/lvca/followers","following_url":"https://api.github.com/users/lvca/following{/other_user}","gists_url":"https://api.github.com/users/lvca/gists{/gist_id}","starred_url":"https://api.github.com/users/lvca/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lvca/subscriptions","organizations_url":"https://api.github.com/users/lvca/orgs","repos_url":"https://api.github.com/users/lvca/repos","events_url":"https://api.github.com/users/lvca/events{/privacy}","received_events_url":"https://api.github.com/users/lvca/received_events","type":"User","site_admin":false}],"milestone":null,"comments":14,"created_at":"2016-08-02T09:56:35Z","updated_at":"2016-08-16T09:39:54Z","closed_at":"2016-08-13T15:56:35Z","body":"## OrientDB Version, operating system, or hardware.\r\n- **v2.2.5**\r\n\r\n## Operating System\r\n- [x] Linux\r\n- [ ] MacOSX\r\n- [ ] Windows\r\n- [ ] Other Unix\r\n- [ ] Other, name? \r\n\r\n## Expected behavior and actual behavior\r\nOur dbase is growing into several TB filesystem size. We have 6 identical servers, spread over 2 datacenters, 3 servers per datacenter.\r\nWhen I want redundancy, and distribution of workload, among these 6 servers, what is the best strategy?\r\nI want to avoid that the full database size gets copied, and synchronised, between all 6 servers. What I think would be more beneficial, is that clusters are spread accross the 6 servers, with for example 3 copies of each cluster (2 in same DC, 1 in alternate DC).\r\nIs that a good strategy to achieve maximum performance (parallel workloads) and space optimisation ?\r\nIf so, how to configure OrientDB for this ?\r\n\r\n## Steps to reproduce the problem\r\n"},"comment":{"url":"https://api.github.com/repos/orientechnologies/orientdb/issues/comments/240054760","html_url":"https://github.com/orientechnologies/orientdb/issues/6497#issuecomment-240054760","issue_url":"https://api.github.com/repos/orientechnologies/orientdb/issues/6497","id":240054760,"user":{"login":"rdelangh","id":15123823,"avatar_url":"https://avatars.githubusercontent.com/u/15123823?v=3","gravatar_id":"","url":"https://api.github.com/users/rdelangh","html_url":"https://github.com/rdelangh","followers_url":"https://api.github.com/users/rdelangh/followers","following_url":"https://api.github.com/users/rdelangh/following{/other_user}","gists_url":"https://api.github.com/users/rdelangh/gists{/gist_id}","starred_url":"https://api.github.com/users/rdelangh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rdelangh/subscriptions","organizations_url":"https://api.github.com/users/rdelangh/orgs","repos_url":"https://api.github.com/users/rdelangh/repos","events_url":"https://api.github.com/users/rdelangh/events{/privacy}","received_events_url":"https://api.github.com/users/rdelangh/received_events","type":"User","site_admin":false},"created_at":"2016-08-16T09:39:54Z","updated_at":"2016-08-16T09:39:54Z","body":"Even more : if there is a concept required of 'owning' server for each cluster in a distributed setup, then what is the advantage of having your clusters distributed over multiple servers ? The mechanisms behind this concept are not very clear to me, how they would still allow to \r\n1) distribute queries that span a single cluster, to be distributed over multiple servers (each one doing part of the work of the query)\r\n2) keep the clusters accessible in all cases (HA) for INSERT as well as SELECT "}}
{"actor":{"display_login":"rdelangh"}}