[
https://issues.apache.org/jira/browse/TRAFODION-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059729#comment-16059729
]
ASF GitHub Bot commented on TRAFODION-2649:
-------------------------------------------
GitHub user zcorrea opened a pull request:
https://github.com/apache/incubator-trafodion/pull/1138
[TRAFODION-2649] Fixed 'rmscheck' method for obtaining status
It now generates the 'rmscheck.sql' logic in a temporary file which obtains
the
node-ids from the 'trafconf' utility. The tempory file is created at
'rmscheck'
invocation.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zcorrea/incubator-trafodion TRAFODION-2649
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-trafodion/pull/1138.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1138
----
commit 616390ca681882472b69687b5a67a7bc680dd2ff
Author: Zalo Correa <[email protected]>
Date: 2017-06-22T17:14:32Z
[TRAFODION-2649] Fixed 'rmscheck' method for obtaining status
It now generates the 'rmscheck.sql' logic in a temporary file which obtains
the
node-ids from the 'trafconf' utility. The tempory file is created at
'rmscheck'
invocation.
----
> Method used in 'rmscheck' script for obtaining status is incompatible with
> elasticity
> -------------------------------------------------------------------------------------
>
> Key: TRAFODION-2649
> URL: https://issues.apache.org/jira/browse/TRAFODION-2649
> Project: Apache Trafodion
> Issue Type: Bug
> Components: foundation
> Affects Versions: 2.2-incubating
> Reporter: Gonzalo E Correa
> Assignee: Gonzalo E Correa
> Fix For: 2.2-incubating
>
>
> The 'sqgen' scripts generate the 'rmscheck.sql' input file invoke by sqlci
> through the rmscheck script. The cluster membership is derived at 'sqgen'
> time which uses the existing node membership at a point in time. Since the
> node membership of the cluster can change at any time after the 'sqgen'
> invocation, the 'rmscheck.sql' input is by definition obsolete when the node
> membership changes, i.e., nodes are added or deleted.
> A different method for obtaining rms status must be implemented.
> The current method generates the following contents of the 'rmschecl.sql'
> input file:
> cat rmscheck.sql
> -- SQ config/utility file generated @ Thu Jun 01 14:00:58 2017
> prepare rms_check from select current_timestamp,
> cast('Node' as varchar(5)),
> cast(tokenstr('nodeId:', variable_info) as varchar(3)) node,
> cast(tokenstr('Status:', variable_info) as varchar(10)) status
> from table(statistics(null, ?));
> execute rms_check using 'RMS_CHECK=0' ;
> execute rms_check using 'RMS_CHECK=1' ;
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)