Uploaded image for project: 'Apache Trafodion (Retired)'
  1. Apache Trafodion (Retired)
  2. TRAFODION-2649

Method used in 'rmscheck' script for obtaining status is incompatible with elasticity

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.2.0
    • 2.2.0
    • foundation
    • None

    Description

      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' ;

      Attachments

        Issue Links

          Activity

            People

              zcorrea Zalo Correa
              zcorrea Zalo Correa
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: