You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/09/27 04:15:00 UTC
[jira] [Commented] (ASTERIXDB-2107) Dynamic Topology Cluster May
Become UNUSABLE on Multiple Nodes Addition
[ https://issues.apache.org/jira/browse/ASTERIXDB-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16181952#comment-16181952 ]
ASF subversion and git services commented on ASTERIXDB-2107:
------------------------------------------------------------
Commit 2c13bdcc8eb5f2bc228aeafe8e4c4ce1481c68a0 in asterixdb's branch refs/heads/master from [~mhubail]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=2c13bdc ]
[ASTERIXDB-2107][CLUS] Prevent Invalid UNUSABLE State in Dynamic Topology
- user model changes: no
- storage format changes: no
- interface changes: yes
Renamed IClusterStateManager add/Remove NCConfig methods
to notifyNode join/failure.
Details:
- Mark node as participant when it completes its startup and
not when it joins the cluster.
- Allow partitions to be added with pending activation state.
- Remove the use of static MetadataProperties for reporting number of nodes.
- Add test cases.
Change-Id: I7a0db2d66cf44650dcc673b3f2de537816cb84c7
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2029
Sonar-Qube: Jenkins <je...@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <je...@fulliautomatix.ics.uci.edu>
Contrib: Jenkins <je...@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <je...@fulliautomatix.ics.uci.edu>
Reviewed-by: Michael Blow <mb...@apache.org>
> Dynamic Topology Cluster May Become UNUSABLE on Multiple Nodes Addition
> -----------------------------------------------------------------------
>
> Key: ASTERIXDB-2107
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2107
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: CLUS - Cluster management
> Reporter: Murtadha Hubail
> Assignee: Murtadha Hubail
>
> A cluster with a dynamic topology will be unusable for a period when two nodes are added to the cluster. When one of two nodes reports startup completion, the cluster state will be updated and the inactive partitions of the second node will be detected which will result in unusable state.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)