[
https://issues.apache.org/jira/browse/TRAFODION-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16349663#comment-16349663
]
ASF GitHub Bot commented on TRAFODION-2650:
-------------------------------------------
GitHub user zcorrea opened a pull request:
https://github.com/apache/trafodion/pull/1437
[TRAFODION-2650] Restructured Trafodion Configuration code into separate
directory structure.
Move code out of monitor source tree into its own directory structure. Move
Trafodion Configuration API header file into the export/include/trafconf
directory.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zcorrea/trafodion TRAFODION-2650
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafodion/pull/1437.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1437
----
commit 87849fcf8199857e0c525d332a061db8744c86cb
Author: Zalo Correa <zalo.correa@...>
Date: 2018-02-02T01:51:35Z
[TRAFODION-2650] Restructured Trafodion Configuration code into separate
directory structure.
----
> The SQLite Trafodion Configuration database storage method can become stale.
> ----------------------------------------------------------------------------
>
> Key: TRAFODION-2650
> URL: https://issues.apache.org/jira/browse/TRAFODION-2650
> Project: Apache Trafodion
> Issue Type: Bug
> Components: foundation
> Affects Versions: 2.2-incubating
> Reporter: Gonzalo E Correa
> Assignee: Gonzalo E Correa
> Priority: Major
> Fix For: 2.3
>
>
> The SQLite storage method can prevent a node from initializing properly. This
> is due to the nature of SQLIte, a database in a file. The file is updated
> locally on each node. In certain failure scenarios, such as Cloudera Manager
> and potentially Ambari installations, the file will not be updated locally.
> This happens when the monitor process is not running and changes are made to
> the configuration, the file in the node where the monitor process is not
> executing will become stale and on a node up event, may contain old
> configuration information.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
