[
https://issues.apache.org/jira/browse/TRAFODION-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gonzalo E Correa updated TRAFODION-2001:
----------------------------------------
Good questions!
With regard to the effect on development practices on workstations, these
changes do not affect the workstation environment. The 'sqgen' script checks
for workstation versus cluster. If it's a workstation environment, the
Trafodion Configuration is repopulated using the contents of the 'sqconfig' and
'sqconfig.persist' text files. This behavior remains the same as before. I will
update the documentation to clarify this point.
With regard to the ilh_traf_restart script on a cluster, currently the 'sqgen'
script returns error information indicating that configuration changes must be
done through the shell's node add/delete commands, and the 'sqstart' command
would still execute using the existing contents of the Trafodion Configuration
database. However, the current bash nodeAdd scripts (nodeAdd_step1 and
nodeAdd_step2) regenerate the 'sqconfig' file with the node section reflecting
the contents of the Trafodion Configuration database after a node has been
added (and in the future will regenerate 'sqconfig.persist' when the persist
add/delete commands are supported). We need to add the ability to clear the
existing Trafodion Configuration database and repopulate it on a subsequent
'sqgen', but this is not currently in place.
A workaround when using the SQLite storage method on a cluster (the only method
currently supported) is to manually delete the 'sqconfig.db' file before
executing 'sqgen' (or more likely executing 'sqstop', removing 'sqconfig.db',
and then executing ilh_traf_restart script). However, this will not work when
other Trafodion Configuration storage methods are enabled, such as Zookeeper,
MySQL, etc.; and a method to clear the database must be implemented.
> 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.1-incubating
> Reporter: Gonzalo E Correa
> Assignee: Gonzalo E Correa
> Fix For: 2.2-incubating
>
> Attachments: TRAFODION-2001-Elasticity.docx,
> TRAFODION-2001-Elasticity.v1.5.docx,
> Trafodion-R2.2-Elasticity-TRAFODON-2001.pptx
>
> 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)
