[ 
https://issues.apache.org/jira/browse/TRAFODION-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000086#comment-16000086
 ] 

ASF GitHub Bot commented on TRAFODION-2001:
-------------------------------------------

Github user zcorrea commented on a diff in the pull request:

    
https://github.com/apache/incubator-trafodion/pull/1077#discussion_r115154601
  
    --- Diff: core/sqf/sql/scripts/sqnodestatus ---
    @@ -26,12 +26,11 @@
     # Implements:
     #   ssh -M "ConnectTimeout 1" -o "ConnectionAttempts 3" n028 hostinfo 2>&1
     #
    -# Uses:
    -#   export MY_NODES=' -w n028 -w n044 -w n029 -w n045 -w n030 -w n031 -w 
n032 '
    +# Uses the following enviroment variables:
     #   export SQ_MON_SSH_OPTIONS=' -o "ConnectTimeout 1" -o 
"ConnectionAttempts 3" '
     #
     
    -my $node_context=lc(readpipe("echo \$NODE_LIST"));
    +my $node_context=readpipe("trafconf -name");
    --- End diff --
    
    The upper lower case is addressed in other code. Specifically, in the 
monitor code. The trafconf utility is new and was created to address the need 
of obtaining the current hostname (node name) membership in a Trafodion cluster 
instance. I will add more details to its purpose and usage in the JIRA: 
TRAFODION-2001. A brief summary is as follows:
    
    - Node membership is initially derived from 'sqconfig' and used to populate 
the Trafodion Configuration database. After this, node membership is through 
the 'shell' node add/delete commands.
    - The Trafodion Configuration database is the configuration of record once 
the instance is started.
    - The 'trafconf' utility reads the contents of the Trafodion Configuration 
database to display the current node membership of the cluster.
    - The 'trafconf' utility us used by scripts and by the Trafodion user 
.bashrc to populate environment variables with the current node membership. 
Specifically, the MY_NODES environment variable.



> Trafodion Elasticity enhancements
> ---------------------------------
>
>                 Key: TRAFODION-2001
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-2001
>             Project: Apache Trafodion
>          Issue Type: New Feature
>          Components: documentation, foundation, installer
>    Affects Versions: 2.2-incubating
>            Reporter: Gonzalo E Correa
>            Assignee: Gonzalo E Correa
>         Attachments: TRAFODION-2001-Elasticity.docx, 
> TRAFODION-2001-Elasticity.v1.4.docx
>
>   Original Estimate: 672h
>  Remaining Estimate: 672h
>
> Abstract
> This JIRA proposes changes to the Apache Trafodion Incubation configuration 
> and operational elements used to define and operate a Trafodion cluster in a 
> Trafodion instance. The changes proposed build on existing functionality for 
> enhancing Trafodion to support elasticity by implementing the ability to add 
> and delete nodes used by Trafodion components.
> The concept of a cluster is defined in Trafodion through the configuration of 
> nodes in the ‘sqconfig’ text file, the Trafodion configuration file. This 
> configuration file is compiled to generate a set of files used to start and 
> stop a Trafodion instance. The files generated consist of a configuration 
> database and scripts which presently contain fixed, i.e., hardcoded, 
> configuration topology attributes of a configured Trafodion instance. This 
> proposal addresses this hardcoded configuration topology issue by adding new 
> configuration commands in the Trafodion Foundation’s monitor components, 
> changing the methodology in the scripts generated, and extending the use of 
> the configuration database currently in use. 
> Objectives
> The objective of this proposal is to implement elasticity capabilities in 
> Trafodion to match or exceed the elasticity capabilities of other modules in 
> the Hadoop eco system.
> This focuses on the Trafodion Foundation functionality. Specifically, the 
> monitor components which use the configuration of nodes that define a 
> Trafodion cluster are enhanced to provide at set of primitive commands to add 
> and delete nodes as well as the generation of events to existing processes in 
> the instance of the addition or deletion of member nodes to the cluster 
> configuration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to