Hi there,
I am trying to follow a distributed query processing example from
Welcome to mclient, the MonetDB/SQL interactive terminal (Jun2016-SP1)
Database: MonetDB v11.23.7 (Jun2016-SP1), 'mapi:monetdb://hnode3.secdev.local:52018/db3'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>CREATE MERGE TABLE mt1 (t int);
operation successful (2.367ms)
sql>CREATE REMOTE TABLE t1 (i int) on 'mapi:monetdb://hnode1.secdev.local:52016/db1';
operation successful (1.287ms)
sql>select * from t1;
+------+
| i |
+======+
| 11 |
| 13 |
+------+
2 tuples (4.694ms)
sql>select count(*) from t1;
Connection lost
sql>select count(*) from t1;
illegal input, not a JSON header (got '')
sql>select count(*) from t1;
Connection lost
sql>select count(*) from t1;
Connection lost
sql>select count(*) from t1;
illegal input, not a JSON header (got '')
sql>select count(*) from t1;
illegal input, not a JSON header (got '')
sql>select count(*) from t1;
an error occurred on connection: Connection lost
sql>select count(*) from t1;
Connection lost
sql>select * from t1;
+------+
| i |
+======+
| 11 |
| 13 |
+------+
2 tuples (508.682ms)
sql>select * from t1;
+------+
| i |
+======+
| 11 |
| 13 |
+------+
2 tuples (6.227ms)
sql>select * from t1;
+------+
| i |
+======+
| 11 |
| 13 |
+------+
2 tuples (5.065ms)
sql>select * from t1;
+------+
| i |
+======+
| 11 |
| 13 |
+------+
2 tuples (4.178ms)
sql>
P.S.
Is there something wrong with my monetdb cluster setup or is it a real bug?
On hnode3 (CentOS 6.8 machine):
[akravchenko@hnode3 ~]$ monetdbd -v
MonetDB Database Server v1.7 (Jun2016-SP1)
[akravchenko@hnode3 ~]$ monetdb discover
location
hnode3.secdev.local:52018*
mapi:monetdb://hnode3.secdev.local:52018/db3
[akravchenko@hnode3 ~]$ monetdb status
name state health remarks
db3 R 20h 100% 11m mapi:monetdb://hnode3.secdev.local:52018/db3
[akravchenko@hnode3 ~]$ monetdbd get all hnode3-dbfarm
property value
hostname hnode3.secdev.local
dbfarm hnode3-dbfarm
status monetdbd[18052] 1.7 (Jun2016-SP1) is serving this dbfarm
mserver /usr/bin/mserver5
logfile hnode3-dbfarm/merovingian.log
pidfile hnode3-dbfarm/merovingian.pid
sockdir /tmp
listenaddr 0.0.0.0
port 52018
exittimeout 60
forward proxy
discovery yes
discoveryttl 600
control yes
passphrase {SHA512}a73f1d86383446438ac64f56e15ada38b41fbb18f029d2181723aeb2acac6a831f60e5fdbd64ac2c8c70e035dd44cbbe3b45565ef2d58feb2821a2078c7fad35
mapisock /tmp/.s.monetdb.52018
controlsock /tmp/.s.merovingian.52018
and on hnode1 (CentOS 6.8 machine):
[akravchenko@hnode1 ~]$ monetdb -v
MonetDB Database Server Toolkit v1.1 (Jun2016-SP1)
[akravchenko@hnode1 ~]$ monetdb discover
location
hnode1.secdev.local:52016*
mapi:monetdb://hnode1.secdev.local:52016/db1
[akravchenko@hnode1 ~]$ monetdb status
name state health remarks
db1 R 4m 15% 32m mapi:monetdb://hnode1.secdev.local:52016/db1
[akravchenko@hnode1 ~]$ monetdbd get all hnode1-dbfarm/
property value
hostname hnode1.secdev.local
dbfarm hnode1-dbfarm/
status monetdbd[1355] 1.7 (Jun2016-SP1) is serving this dbfarm
mserver /usr/bin/mserver5
logfile hnode1-dbfarm//merovingian.log
pidfile hnode1-dbfarm//merovingian.pid
sockdir /tmp
listenaddr 0.0.0.0
port 52016
exittimeout 60
forward proxy
discovery yes
discoveryttl 600
control yes
passphrase {SHA512}a73f1d86383446438ac64f56e15ada38b41fbb18f029d2181723aeb2acac6a831f60e5fdbd64ac2c8c70e035dd44cbbe3b45565ef2d58feb2821a2078c7fad35
mapisock /tmp/.s.monetdb.52016
controlsock /tmp/.s.merovingian.52016
[akravchenko@hnode1 ~]$
Thank you,
Anton