-
Notifications
You must be signed in to change notification settings - Fork 45
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
RONDB-785: Added new command to set LocationDomainId in ndb_mgm
- Loading branch information
1 parent
7d7235d
commit c49a5af
Showing
43 changed files
with
1,755 additions
and
44 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,173 @@ | ||
Configuration changed to reflect new location domain id of node 1 | ||
Now changing location domain id in the cluster | ||
Node 1 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 2 | ||
Now changing location domain id in the cluster | ||
Node 2 now has location domain id 2 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 16 | ||
Now changing location domain id in the cluster | ||
Node 16 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 32 | ||
Now changing location domain id in the cluster | ||
Node 32 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 48 | ||
Now changing location domain id in the cluster | ||
Node 48 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 49 | ||
Now changing location domain id in the cluster | ||
Node 49 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 63 | ||
Now changing location domain id in the cluster | ||
Node 63 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 127 | ||
Now changing location domain id in the cluster | ||
Node 127 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 192 | ||
Now changing location domain id in the cluster | ||
Node 192 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 228 | ||
Now changing location domain id in the cluster | ||
Node 228 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 229 | ||
Now changing location domain id in the cluster | ||
Node 229 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 230 | ||
Now changing location domain id in the cluster | ||
Node 230 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 231 | ||
Now changing location domain id in the cluster | ||
Node 231 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 232 | ||
Now changing location domain id in the cluster | ||
Node 232 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 233 | ||
Now changing location domain id in the cluster | ||
Node 233 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 255 | ||
Now changing location domain id in the cluster | ||
Node 255 now has location domain id 1 in the cluster | ||
|
||
create table t1 (a int not null primary key) engine ndb; | ||
insert into t1 values (0),(1),(2),(3); | ||
select * from t1 order by a; | ||
a | ||
0 | ||
1 | ||
2 | ||
3 | ||
|
||
select a from t1 where a = 0; | ||
a | ||
0 | ||
select a from t1 where a = 1; | ||
a | ||
1 | ||
select a from t1 where a = 2; | ||
a | ||
2 | ||
select a from t1 where a = 3; | ||
a | ||
3 | ||
|
||
Configuration changed to reflect new location domain id of node 1 | ||
Now changing location domain id in the cluster | ||
Node 1 now has location domain id 2 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 2 | ||
Now changing location domain id in the cluster | ||
Node 2 now has location domain id 1 in the cluster | ||
|
||
|
||
select a from t1 where a = 0; | ||
a | ||
0 | ||
select a from t1 where a = 1; | ||
a | ||
1 | ||
select a from t1 where a = 2; | ||
a | ||
2 | ||
select a from t1 where a = 3; | ||
a | ||
3 | ||
|
||
drop table t1; | ||
Configuration changed to reflect new location domain id of node 1 | ||
Now changing location domain id in the cluster | ||
Node 1 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 2 | ||
Now changing location domain id in the cluster | ||
Node 2 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 16 | ||
Now changing location domain id in the cluster | ||
Node 16 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 32 | ||
Now changing location domain id in the cluster | ||
Node 32 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 48 | ||
Now changing location domain id in the cluster | ||
Node 48 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 49 | ||
Now changing location domain id in the cluster | ||
Node 49 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 63 | ||
Now changing location domain id in the cluster | ||
Node 63 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 127 | ||
Now changing location domain id in the cluster | ||
Node 127 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 192 | ||
Now changing location domain id in the cluster | ||
Node 192 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 228 | ||
Now changing location domain id in the cluster | ||
Node 228 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 229 | ||
Now changing location domain id in the cluster | ||
Node 229 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 230 | ||
Now changing location domain id in the cluster | ||
Node 230 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 231 | ||
Now changing location domain id in the cluster | ||
Node 231 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 232 | ||
Now changing location domain id in the cluster | ||
Node 232 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 233 | ||
Now changing location domain id in the cluster | ||
Node 233 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 255 | ||
Now changing location domain id in the cluster | ||
Node 255 now has location domain id 0 in the cluster | ||
|
220 changes: 220 additions & 0 deletions
220
mysql-test/suite/ndb/r/ndb_location_domain_id_2ng.result
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,220 @@ | ||
Configuration changed to reflect new location domain id of node 1 | ||
Now changing location domain id in the cluster | ||
Node 1 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 2 | ||
Now changing location domain id in the cluster | ||
Node 2 now has location domain id 2 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 3 | ||
Now changing location domain id in the cluster | ||
Node 3 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 4 | ||
Now changing location domain id in the cluster | ||
Node 4 now has location domain id 2 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 16 | ||
Now changing location domain id in the cluster | ||
Node 16 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 32 | ||
Now changing location domain id in the cluster | ||
Node 32 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 48 | ||
Now changing location domain id in the cluster | ||
Node 48 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 49 | ||
Now changing location domain id in the cluster | ||
Node 49 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 63 | ||
Now changing location domain id in the cluster | ||
Node 63 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 127 | ||
Now changing location domain id in the cluster | ||
Node 127 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 192 | ||
Now changing location domain id in the cluster | ||
Node 192 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 228 | ||
Now changing location domain id in the cluster | ||
Node 228 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 229 | ||
Now changing location domain id in the cluster | ||
Node 229 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 230 | ||
Now changing location domain id in the cluster | ||
Node 230 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 231 | ||
Now changing location domain id in the cluster | ||
Node 231 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 232 | ||
Now changing location domain id in the cluster | ||
Node 232 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 233 | ||
Now changing location domain id in the cluster | ||
Node 233 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 255 | ||
Now changing location domain id in the cluster | ||
Node 255 now has location domain id 1 in the cluster | ||
|
||
create table t1 (a int not null primary key) engine ndb; | ||
create table t2 (b int not null primary key) engine ndb; | ||
insert into t1 values (0),(1),(2),(3); | ||
insert into t2 values (0),(1),(2),(3); | ||
select * from t1; | ||
a | ||
2 | ||
3 | ||
0 | ||
1 | ||
|
||
|
||
select a from t1 order by a; | ||
a | ||
0 | ||
1 | ||
2 | ||
3 | ||
select t1.a,t2.b from t1, t2 WHERE t1.a = t2.b order by t1.a; | ||
a b | ||
0 0 | ||
1 1 | ||
2 2 | ||
3 3 | ||
|
||
|
||
|
||
|
||
select a from t1 order by a; | ||
a | ||
0 | ||
1 | ||
2 | ||
3 | ||
select t1.a,t2.b from t1, t2 WHERE t1.a = t2.b order by t1.a; | ||
a b | ||
0 0 | ||
1 1 | ||
2 2 | ||
3 3 | ||
|
||
|
||
Configuration changed to reflect new location domain id of node 1 | ||
Now changing location domain id in the cluster | ||
Node 1 now has location domain id 2 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 2 | ||
Now changing location domain id in the cluster | ||
Node 2 now has location domain id 1 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 3 | ||
Now changing location domain id in the cluster | ||
Node 3 now has location domain id 2 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 4 | ||
Now changing location domain id in the cluster | ||
Node 4 now has location domain id 1 in the cluster | ||
|
||
|
||
|
||
select a from t1 order by a; | ||
a | ||
0 | ||
1 | ||
2 | ||
3 | ||
select t1.a,t2.b from t1, t2 WHERE t1.a = t2.b order by t1.a; | ||
a b | ||
0 0 | ||
1 1 | ||
2 2 | ||
3 3 | ||
|
||
|
||
drop table t1; | ||
drop table t2; | ||
Configuration changed to reflect new location domain id of node 1 | ||
Now changing location domain id in the cluster | ||
Node 1 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 2 | ||
Now changing location domain id in the cluster | ||
Node 2 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 3 | ||
Now changing location domain id in the cluster | ||
Node 3 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 4 | ||
Now changing location domain id in the cluster | ||
Node 4 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 16 | ||
Now changing location domain id in the cluster | ||
Node 16 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 32 | ||
Now changing location domain id in the cluster | ||
Node 32 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 48 | ||
Now changing location domain id in the cluster | ||
Node 48 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 49 | ||
Now changing location domain id in the cluster | ||
Node 49 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 63 | ||
Now changing location domain id in the cluster | ||
Node 63 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 127 | ||
Now changing location domain id in the cluster | ||
Node 127 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 192 | ||
Now changing location domain id in the cluster | ||
Node 192 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 228 | ||
Now changing location domain id in the cluster | ||
Node 228 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 229 | ||
Now changing location domain id in the cluster | ||
Node 229 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 230 | ||
Now changing location domain id in the cluster | ||
Node 230 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 231 | ||
Now changing location domain id in the cluster | ||
Node 231 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 232 | ||
Now changing location domain id in the cluster | ||
Node 232 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 233 | ||
Now changing location domain id in the cluster | ||
Node 233 now has location domain id 0 in the cluster | ||
|
||
Configuration changed to reflect new location domain id of node 255 | ||
Now changing location domain id in the cluster | ||
Node 255 now has location domain id 0 in the cluster | ||
|
Oops, something went wrong.