[MCOL-422] Amazon AMI single-server Columnstore didn't restart on a stop/start Created: 2016-11-28  Updated: 2023-10-26  Resolved: 2016-12-09

Status: Closed
Project: MariaDB ColumnStore
Component/s: ?
Affects Version/s: 1.0.5
Fix Version/s: 1.0.6

Type: Bug Priority: Major
Reporter: David Hill (Inactive) Assignee: David Hill (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Environment:

amazon ami install, which is a non-root install

Sprint: 2016-23, 2016-24

 Description   

Columnstore failed to automatically startup when the instance was stopped/started.

getsysteminfo Mon Nov 28 16:49:23 2016

System columnstore-1

System and Module statuses

Component Status Last Status Change
------------ -------------------------- ------------------------
System MAN_OFFLINE

MariaDB Columnstore Process statuses

Process Module Status Last Status Change Process ID
------------------ ------ --------------- ------------------------ ----------

        • printProcessStatus Failed = API Failure return in getProcessStatus API

Nov 28 16:29:25 ip-172-30-0-153 messagequeue[4390]: 25.539482 |0|0|0| W 31 CAL0071: InetStreamSocket::read: EOF during readToMagic: socket read error: Success; InetStreamSocket: sd: 11 inet: 127.0.0.1 port: 8630; Will retry.

 Comments   
Comment by David Hill (Inactive) [ 2016-12-04 ]

Did come up with a fix after an epic battle...

First the command for non-root to autostart on reboot wasn't added and this is the command has been used in the past:

But on a Amazon Centos 7 EC2 instance, I couldn't get the command above to work 100% of the time. Not sure why.. So I did find another command that works and placed it in /etc/rc.d/rclocal:

runuser -l mariadb-user -c "/home/mariadb-user/mariadb/columnstore/bin/columnstore start"

So this resolved this issue, but during this test, ran into another issue which is being investigated:

DecomSvr fails to start after a instance is stop/started

MCOL-434

Comment by David Hill (Inactive) [ 2016-12-04 ]

tested multi-node, ColumnStore did start, so the fix works. But the system didn't successfully start. Open MCOL-435..

Comment by David Hill (Inactive) [ 2016-12-04 ]

Using the new MariaDB-ColumnStore-1.0.6 AMI, create both a single-server install and a multi-node install. After each is successfully lauched, stop/start thje associated instances and make sure that the ColumnStore system starts ups on all nodes.

Use and make sure a ProcMon is launched on each system

  1. ma getsystemi
Comment by David Hill (Inactive) [ 2016-12-09 ]

testing on amazon ec2 with latest AMI, MariaDB-ColumnStore-1.0

Generated at Thu Feb 08 02:20:57 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.