[
https://issues.apache.org/jira/browse/TRAFODION-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16029838#comment-16029838
]
Carol Pearson commented on TRAFODION-2001:
------------------------------------------
Wow, this is a big change with some complexity to it. I've tested it by
running transactional and non-transactional workloads, and pushing it to
moderate levels, including many tables with millions of rows and it works fine.
This change fundamentally changes how the cluster defines itself, so I also
observed what happened when I downed nodes in sqshell and rebooted servers,
with and without workloads running, and it holds together nicely.
> 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)