Memsql-ops commands with 6.7

Help
1

Hi,

I know the memsql-ops are deprecated from 6.7 but then we are advised from the memsql team that we can still use memsql-ops for sometime.

After upgrading memsql from 5.x to 6.x and registering the nodes, I am getting a strange errors using memsql-ops commands as show below.

Example 1:

I am trying to stop the leaf node, but the error shows it is already stopped.

[root@ip-10-251-40-73 master-43306-MIf274ff1e]# memsql-admin list-nodes
±-----------±-------±----------±------±--------------±-------------±--------±---------------±-------------------+
| MemSQL ID | Role | Host | Port | Process State | Connectable? | Version | Recovery State | Availability Group |
±-----------±-------±----------±------±--------------±-------------±--------±---------------±-------------------+
| B4C9F4EB9C | Master | 127.0.0.1 | 43306 | Running | True | 6.7.18 | Online | |
| 352191F3B8 | Leaf | 127.0.0.1 | 43307 | Running | True | 6.7.18 | Online | 1 |
±-----------±-------±----------±------±--------------±-------------±--------±---------------±-------------------+
[root@ip-10-251-40-73 master-43306-MIf274ff1e]# memsql-ops memsql-stop
Index ID Agent Id Process State Cluster State Role Host Port Version
1 B4C9F4E Aa3e2cc RUNNING CONNECTED MASTER 127.0.0.1 43306 6.7.18
2 352191F Aa3e2cc RUNNING CONNECTED LEAF 127.0.0.1 43307 6.7.18
3 All MemSQL nodes
Select an option: 2
2019-05-29 08:59:56: J146e53 [INFO] Stopping MemSQL node 352191F3B84627A71FB56009232CBA5A552ABF28 on Agent Aa3e2ccd00cb24c36a528f875121bb918
2019-05-29 08:59:56: J146e53 [INFO] MemSQL node 352191F3B84627A71FB56009232CBA5A552ABF28 is already stopped

Example 2:

memsql-ops memsql-start also seems not working as intended as show below

[root@ip-10-251-40-73 master-43306-MIf274ff1e]# memsql-ops memsql-start
Index ID Agent Id Process State Cluster State Role Host Port Version
1 B4C9F4E Aa3e2cc RUNNING CONNECTED MASTER 127.0.0.1 43306 6.7.18
2 352191F Aa3e2cc NOT RUNNING OFFLINE LEAF 127.0.0.1 43307 6.7.18
3 All MemSQL nodes
Select an option: 3
Starting cluster
MemSQL node 352191F3B84627A71FB56009232CBA5A552ABF28 failed to start: Failed to start MemSQL: Could not retrieve MemSQL ID: [Errno 2] No such file or directory: ‘data/memsql_id’

Is this an expected behaviour since the tool is deprecated?

2

Hi Memsql team,

Any update on this.

3

Hi Kishore, it looks like you may be using both the old memsql Ops and the newwer memsql tools concurrently, which may be leading to issues.

Can you provide some more information by running “memsql-ops report” and “memsql-report check” and providing the results here?

4

@mbhakti yes, i have installed both the memsql ops and memsql tools, so I was using both. I have installed and did a fresh installation with 5.8.4 and upgraded, I do see now memsql-ops is working , but still the memsql-tools are not working, ass memsqlctl is not available which is used for registering the nodes.

Shouldn’t we use the memsql-ops and memsql tools concurrently? I did not find the steps to configure memsql-tools after the upgrade.

I have followed memsql- upgrade and also install the memsql-tools, what are the steps I need to take to make the memsql-ops and memsql tools to work?

5

Hello Kishore,

It’s not possible to run memsql-ops and memsql-tools at the same time. I recommend you continue to use memsql-ops and to remove memsql-tools.

Kind regards,
Cindy