[jira] [Created] (TRAFODION-1651) dcsstop will not stop the connected mxosrvr and no message to tell this (it will cause confusion when connected to the old one)

["Jianguo Zhou (Jason) (JIRA)" <ji...@apache.org>]

Jianguo Zhou (Jason) created TRAFODION-1651:
-----------------------------------------------

             Summary: dcsstop will not stop the connected mxosrvr and no message to tell this (it will cause confusion when connected to the old one)
                 Key: TRAFODION-1651
                 URL: https://issues.apache.org/jira/browse/TRAFODION-1651
             Project: Apache Trafodion
          Issue Type: Bug
          Components: connectivity-dcs
            Reporter: Jianguo Zhou (Jason)


I sometimes changed the dcs-site.xml file and need to restart DCS using dcsstop, but even after restart, I run into issue shows seems like my configuration doesn’t take effect, after some check and notice that two dcsserver was not restarted for I have trafci connected on it before restart, and those two connected dcsserver never get restarted, but there was no message saying that, and it caused the confusion, so we need to let the user know in some way to avoid it.
trafodion@suse-4:~/esgynDB-20151119_0900-bin/dcs-2.0.0/conf> dcsstop     Stop DCS
/home/trafodion/esgynDB-20151119_0900-bin/dcs-2.0.0/bin/stop-dcs.sh found.
Shutting down the DCS environment now
stopping master.
suse-4: stopping server.
suse-5: stopping server.
suse-6: stopping server.                                              No error or warning message

trafodion@suse-5:~/esgynDB-20151119_0900-bin/dcs-2.0.0/bin> dcscheck    Check and there are 2 not stopped

DcsMaster is not started. Please start DCS using 'dcsstart' command...

Process         Configured      Actual          Down
---------       ----------      ------          ----
DcsMaster       1               0               1
DcsServer       3               0               3
mxosrvr         12              2               10

trafodion@suse-4:~/esgynDB-20151119_0900-bin/dcs-2.0.0/conf> dcsstart     Start DCS and it will up with configured number of mxosrvrs, but the number include those 2 not restarted, so it may cause confusion issue if we don’t notice this
The Trafodion monitor seems to be running on this node - let's check the status...
Checking if processes are up.
Checking attempt: 1; user specified max: 2. Execution time in seconds: 0.

The SQ environment is up!


Process         Configured      Actual      Down
-------         ----------      ------      ----
DTM             3               3           
RMS             6               6           
MXOSRVR         12              2           10

/home/trafodion/esgynDB-20151119_0900-bin/dcs-2.0.0/bin/start-dcs.sh found.
Starting the DCS environment now
starting master, logging to /home/trafodion/esgynDB-20151119_0900-bin/dcs-2.0.0/bin/../logs/dcs-trafodion-1-master-suse-4.out
suse-4: starting server, logging to /home/trafodion/esgynDB-20151119_0900-bin/dcs-2.0.0/bin/../logs/dcs-trafodion-1-server-suse-4.out
suse-5: starting server, logging to /home/trafodion/esgynDB-20151119_0900-bin/dcs-2.0.0/bin/../logs/dcs-trafodion-2-server-suse-5.out
suse-6: starting server, logging to /home/trafodion/esgynDB-20151119_0900-bin/dcs-2.0.0/bin/../logs/dcs-trafodion-3-server-suse-6.out

trafodion@suse-5:~/esgynDB-20151119_0900-bin/dcs-2.0.0/bin> dcscheck

Zookeeper is listening on port 2181
DcsMaster is listening on port 23400

Process         Configured      Actual          Down
---------       ----------      ------          ----
DcsMaster       1               1
DcsServer       3               3
mxosrvr         12              12





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)