[
https://issues.apache.org/jira/browse/TRAFODION-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277109#comment-15277109
]
Gonzalo E Correa commented on TRAFODION-1980:
---------------------------------------------
There are two issues contributing to this behavior.
1. Analysis indicates that the 'shell' initialization logic is setting the
state of physical node object to 'StateUp'.
2. The method used to determine the physical state of a node is the use of an
environment variable, i.e., NODE_LIST, which contains a list of host names
which make up the cluster. This list is used to execute an 'ssh <node-list>
hostname' command across all the nodes. The hostnames returned are the nodes
that are in an 'UP' state. However, if NODE_LIST does not contain a name, the
state of the physical node object is not updated due to an early termination of
the logic loop that sets the operational state of the physical node.
This causes subsequent request processing to honor the 'UP' request attempting
to process it on a non-existent node, and it hangs.
Changing the initialization logic of physical node objects to a 'StateDown'
appears to fix the behavior.
> Node up command (sqshell), when targeting a non-existing node, hangs.
> ---------------------------------------------------------------------
>
> Key: TRAFODION-1980
> URL: https://issues.apache.org/jira/browse/TRAFODION-1980
> Project: Apache Trafodion
> Issue Type: Bug
> Components: foundation
> Affects Versions: 2.1-incubating
> Reporter: Gonzalo E Correa
> Assignee: Gonzalo E Correa
> Fix For: 2.1-incubating
>
>
> When testing JIRA TRAFODION-1885 and targeting a node that does not exist and
> is not set in the TRAF_EXCLUDE_LIST environment variable. The 'up' command
> attempts to process and hangs. It should be returning an error indicating
> that the node is not available.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
