Skip to content
This repository has been archived by the owner on Feb 11, 2022. It is now read-only.

New cluster configuration #38

Open
rtsisyk opened this issue Oct 16, 2017 · 0 comments
Open

New cluster configuration #38

rtsisyk opened this issue Oct 16, 2017 · 0 comments
Assignees
@Gerold103
Milestone
2.0

Comments

@rtsisyk
Copy link
Contributor

rtsisyk commented Oct 16, 2017 •
edited
Loading

Rename zone to repliacaset and make this option mandatory:

shard.init {
    servers = {
           { uri = '10.0.0.21:3301', replicaset=1 },
           { uri = '10.0.0.22:3301', replicaset=1 },

           { uri = '10.0.0.21:3302', replicaset=2 },
           { uri = '10.0.0.22:3302', replicaset=2 },

           { uri = '10.0.0.21:3303', replicaset=3 },
           { uri = '10.0.0.22:3303', replicaset=3 },
    },

    login = 'guest',
    password = '',
    redundancy = 3
}
  • Every replicaset must have at least 'redundancy' nodes, otherwise configuration should be considered as is invalid.
  • Remove support for replication = false from the configuration.
@rtsisyk rtsisyk added this to the 2.0 milestone Oct 16, 2017
Gerold103 added a commit that referenced this issue Oct 17, 2017
@Gerold103
Remove replication=false, bug fixes
73a2fba 
* Use test_run cluster utils to manage shard nodes. Always use
replication to manage redundancy.
* Fix the bug in shard init: make all shard_init_v...() in a single
box.once(), else some nodes can skip a first box.once() but start
a second box.once() before the first one is finished.

Part of #38
Gerold103 added a commit that referenced this issue Oct 17, 2017
@Gerold103
Remove replication=false, bug fixes
0a4eee7 
* Use test_run cluster utils to manage shard nodes. Always use
replication to maintain redundancy.
* Fix the bug in shard init: make all shard_init_v...() in a single
box.once(), else some nodes can skip a first box.once() but start
a second box.once() before the first one is finished.
* Validate shard.init options.

Part of #38
Gerold103 added a commit that referenced this issue Oct 18, 2017
@Gerold103
Remove replication=false, bug fixes
2e9e86b 
* Use test_run cluster utils to manage shard nodes. Always use
replication to maintain redundancy.
* Validate shard.init options.

Part of #38
rtsisyk pushed a commit that referenced this issue Oct 18, 2017
@Gerold103 @rtsisyk
Remove replication=false, bug fixes
80cff72 
* Use test_run cluster utils to manage shard nodes. Always use
replication to maintain redundancy.
* Validate shard.init options.

Part of #38
Gerold103 added a commit that referenced this issue Oct 18, 2017
@Gerold103
Introduce replica set
727e954 
* Remove dead code;
* Remove zones from connpool;
* Replace shard zones with replica sets;
* Fix minor bugs;
* Check cfg and minimal redundancy;
* Refactoring.

Closes #38
Gerold103 added a commit that referenced this issue Oct 19, 2017
@Gerold103
Introduce replica set and shard.call
47912ab 
* Remove dead code;
* Remove zones from connpool;
* Replace shard zones with replica sets;
* Introduce shard.call function to call any function by a given key
  on a corresponding replica set;
* Fix minor bugs;
* Check cfg and minimal redundancy;
* Refactoring.

Closes #38
rtsisyk pushed a commit that referenced this issue Oct 20, 2017
@Gerold103 @rtsisyk
Introduce replica set and shard.call
92c7b41 
* Remove dead code;
* Remove zones from connpool;
* Replace shard zones with replica sets;
* Introduce shard.call function to call any function by a given key
  on a corresponding replica set;
* Fix minor bugs;
* Check cfg and minimal redundancy;
* Refactoring.

Closes #38
@knazarov knazarov mentioned this issue Jan 17, 2018
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Gerold103 Gerold103

Labels
None yet
Projects
None yet
Milestone
2.0
Development

No branches or pull requests
2 participants
@rtsisyk @Gerold103