Project

General

Profile

Task #3545

Story #3882: Refactor hzNodes out of CN Node Registry

hzNodes expose unapproved Nodes

Added by Robert Waltz about 11 years ago. Updated over 8 years ago.

Status:
Rejected
Priority:
Urgent
Assignee:
Robert Waltz
Category:
d1_cn_node_registry
Target version:
Start date:
2013-02-01
Due date:
2013-03-16
% Done:

0%

Estimated time:
0.00 h
Milestone:
CCI-1.4
Product Version:
*
Story Points:
Sprint:

Description

hzNodes must be pulling from the wrong query to retrieve all the nodes instead of the nodelist only.

hzNodes will eventually go away in deference to a better change notification mechanism. But until then, change the code to pull only approved nodes since it is messing up replication.

Use public api in replication. Maybe use some caching as well so that you do not hit the endpoint continuously.

History

#1 Updated by Robert Waltz about 11 years ago

It think this may be due to the fact that replication will get a node that is listed as an authoritative node or some other node id entry found in the systememetadata. The call to getNode on the hzNode map will retrieve any valid node id regardless of whether it is approved or not. I created a getApprovedNode for the HazelcastLdapStore.

#2 Updated by Robert Waltz about 11 years ago

  • Status changed from New to In Progress

#3 Updated by Robert Waltz about 11 years ago

  • Target version changed from 2013.4-Block.1.2 to 2013.6-Block.1.3
  • Due date changed from 2013-02-02 to 2013-02-06

#4 Updated by Robert Waltz about 11 years ago

  • Description updated (diff)
  • Due date changed from 2013-02-06 to 2013-03-16
  • Milestone changed from CCI-1.1.1 to CCI-1.1.2
  • Target version changed from 2013.6-Block.1.3 to 2013.10-Block.2.1
  • Assignee changed from Robert Waltz to Chris Jones

#5 Updated by Robert Waltz over 10 years ago

  • Target version changed from 2013.10-Block.2.1 to 2013.33-Block.4.4

#6 Updated by Robert Waltz over 10 years ago

  • Parent task set to #3882
  • Assignee changed from Chris Jones to Robert Waltz

#7 Updated by Robert Waltz over 10 years ago

  • Target version changed from 2013.33-Block.4.4 to 2013.37-Block.5.2

#8 Updated by Robert Waltz over 10 years ago

  • Estimated time set to 0.00
  • Milestone changed from CCI-1.1.2 to CCI-1.3

#9 Updated by Robert Waltz over 10 years ago

  • Target version changed from 2013.37-Block.5.2 to 2013.33-Block.4.4

#10 Updated by Robert Waltz over 10 years ago

  • Target version changed from 2013.33-Block.4.4 to 2013.46-Block.6.2

#11 Updated by Robert Waltz over 10 years ago

  • Product Version set to 1.2.1
  • Milestone changed from CCI-1.3 to CCI-1.2

#12 Updated by Chris Jones over 10 years ago

  • Target version changed from 2013.46-Block.6.2 to 2014.8-Block.1.4

#13 Updated by Robert Waltz over 10 years ago

  • Target version changed from 2014.8-Block.1.4 to 2014.6-Block.1.3

#14 Updated by Robert Waltz about 10 years ago

  • Target version changed from 2014.6-Block.1.3 to 2014.14-Block.2.3

#15 Updated by Robert Waltz almost 10 years ago

  • Target version changed from 2014.14-Block.2.3 to 2014.28-Block.4.2

#16 Updated by Robert Waltz over 9 years ago

  • Product Version changed from 1.2.1 to *
  • Milestone changed from CCI-1.2 to CCI-1.4

#17 Updated by Robert Waltz over 9 years ago

  • Target version deleted (2014.28-Block.4.2)

#18 Updated by Robert Waltz over 9 years ago

  • Target version set to Maintenance Backlog

#19 Updated by Robert Waltz over 9 years ago

  • Target version changed from Maintenance Backlog to Release Backlog

#20 Updated by Robert Waltz over 9 years ago

  • Target version changed from Release Backlog to CCI-2.1.0

#21 Updated by Robert Waltz over 8 years ago

  • Status changed from In Progress to Rejected

hzNodes has been factored out of Hazelcast for V2.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)