[jira] [Updated] (IGNITE-19506) Use data nodes from DistributionZoneManager with a causality token instead of BaselineManager#nodes
[ https://issues.apache.org/jira/browse/IGNITE-19506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-19506: - Ignite Flags: (was: Docs Required,Release Notes Required) > Use data nodes from DistributionZoneManager with a causality token instead of > BaselineManager#nodes > --- > > Key: IGNITE-19506 > URL: https://issues.apache.org/jira/browse/IGNITE-19506 > Project: Ignite > Issue Type: Bug >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Attachments: Causality data nodes.docx > > Time Spent: 7h > Remaining Estimate: 0h > > h3. *Motivation* > Need to use data nodes from DistributionZoneManager instead of > BaselineManager#nodes in all places except of in-memory raft > (TableManager#calculateAssignments) > We need to get data nodes consistently so we need to use revision of > configuration events and a meta storage events as causality token. > Description of causality data nodes algorithm is attached. > h3. *Definition of Done* > Implement method DistributionZoneManager#dataNodes to obtaining data nodes > from zone manager with causality token. > Use this method instead of BaselineManager#nodes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19506) Use data nodes from DistributionZoneManager with a causality token instead of BaselineManager#nodes
[ https://issues.apache.org/jira/browse/IGNITE-19506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Uttsel updated IGNITE-19506: --- Description: h3. *Motivation* Need to use data nodes from DistributionZoneManager instead of BaselineManager#nodes in all places except of in-memory raft (TableManager#calculateAssignments) We need to get data nodes consistently so we need to use revision of configuration events and a meta storage events as causality token. Description of causality data nodes algorithm is attached. h3. *Definition of Done* Implement method DistributionZoneManager#dataNodes to obtaining data nodes from zone manager with causality token. Use this method instead of BaselineManager#nodes. was: h3. *Motivation* Need to use data nodes from DistributionZoneManager instead of BaselineManager#nodes in: # DistributionZoneRebalanceEngine#onUpdateReplicas # TableManager#createAssignmentsSwitchRebalanceListener We need to get data nodes consistently so we need to use revision of configuration events and a meta storage events as causality token. Also need to use VersionedValue to save data nodes with causality token. Description of causality data nodes algorithm is attached. h3. *Definition of Done* DistributionZoneRebalanceEngine#onUpdateReplicas and TableManager#createAssignmentsSwitchRebalanceListener use data nodes from DistributionZoneManager > Use data nodes from DistributionZoneManager with a causality token instead of > BaselineManager#nodes > --- > > Key: IGNITE-19506 > URL: https://issues.apache.org/jira/browse/IGNITE-19506 > Project: Ignite > Issue Type: Bug >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Major > Labels: ignite-3 > Attachments: Causality data nodes.docx > > Time Spent: 5h 20m > Remaining Estimate: 0h > > h3. *Motivation* > Need to use data nodes from DistributionZoneManager instead of > BaselineManager#nodes in all places except of in-memory raft > (TableManager#calculateAssignments) > We need to get data nodes consistently so we need to use revision of > configuration events and a meta storage events as causality token. > Description of causality data nodes algorithm is attached. > h3. *Definition of Done* > Implement method DistributionZoneManager#dataNodes to obtaining data nodes > from zone manager with causality token. > Use this method instead of BaselineManager#nodes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19506) Use data nodes from DistributionZoneManager with a causality token instead of BaselineManager#nodes
[ https://issues.apache.org/jira/browse/IGNITE-19506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Uttsel updated IGNITE-19506: --- Attachment: Causality data nodes.docx > Use data nodes from DistributionZoneManager with a causality token instead of > BaselineManager#nodes > --- > > Key: IGNITE-19506 > URL: https://issues.apache.org/jira/browse/IGNITE-19506 > Project: Ignite > Issue Type: Bug >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Major > Labels: ignite-3 > Attachments: Causality data nodes.docx > > Time Spent: 1h > Remaining Estimate: 0h > > h3. *Motivation* > Need to use data nodes from DistributionZoneManager instead of > BaselineManager#nodes in: > # DistributionZoneRebalanceEngine#onUpdateReplicas > # TableManager#createAssignmentsSwitchRebalanceListener > We need to get data nodes consistently so we need to use revision of > configuration events and a meta storage events as causality token. Also need > to use VersionedValue to save data nodes with causality token. > Description of causality data nodes algorithm is attached. > h3. *Definition of Done* > DistributionZoneRebalanceEngine#onUpdateReplicas and > TableManager#createAssignmentsSwitchRebalanceListener use data nodes from > DistributionZoneManager -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19506) Use data nodes from DistributionZoneManager with a causality token instead of BaselineManager#nodes
[ https://issues.apache.org/jira/browse/IGNITE-19506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Uttsel updated IGNITE-19506: --- Description: h3. *Motivation* Need to use data nodes from DistributionZoneManager instead of BaselineManager#nodes in: # DistributionZoneRebalanceEngine#onUpdateReplicas # TableManager#createAssignmentsSwitchRebalanceListener We need to get data nodes consistently so we need to use revision of configuration events and a meta storage events as causality token. Also need to use VersionedValue to save data nodes with causality token. Description of causality data nodes algorithm is attached. h3. *Definition of Done* DistributionZoneRebalanceEngine#onUpdateReplicas and TableManager#createAssignmentsSwitchRebalanceListener use data nodes from DistributionZoneManager was: h3. *Motivation* Need to use data nodes from DistributionZoneManager instead of BaselineManager#nodes in: # DistributionZoneRebalanceEngine#onUpdateReplicas # TableManager#createAssignmentsSwitchRebalanceListener We need to get data nodes consistently so we need to use revision of configuration events and a meta storage events as causality token. Also need to use VersionedValue to save data nodes with causality token. Description of causality data nodes algorithm: https://docs.google.com/document/d/1fq7HpHNF-hFEv8w8oIQCLAZObj3s5klrbQxuhsF7Dy0 h3. *Definition of Done* DistributionZoneRebalanceEngine#onUpdateReplicas and TableManager#createAssignmentsSwitchRebalanceListener use data nodes from DistributionZoneManager > Use data nodes from DistributionZoneManager with a causality token instead of > BaselineManager#nodes > --- > > Key: IGNITE-19506 > URL: https://issues.apache.org/jira/browse/IGNITE-19506 > Project: Ignite > Issue Type: Bug >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Major > Labels: ignite-3 > Attachments: Causality data nodes.docx > > Time Spent: 1h > Remaining Estimate: 0h > > h3. *Motivation* > Need to use data nodes from DistributionZoneManager instead of > BaselineManager#nodes in: > # DistributionZoneRebalanceEngine#onUpdateReplicas > # TableManager#createAssignmentsSwitchRebalanceListener > We need to get data nodes consistently so we need to use revision of > configuration events and a meta storage events as causality token. Also need > to use VersionedValue to save data nodes with causality token. > Description of causality data nodes algorithm is attached. > h3. *Definition of Done* > DistributionZoneRebalanceEngine#onUpdateReplicas and > TableManager#createAssignmentsSwitchRebalanceListener use data nodes from > DistributionZoneManager -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19506) Use data nodes from DistributionZoneManager with a causality token instead of BaselineManager#nodes
[ https://issues.apache.org/jira/browse/IGNITE-19506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirza Aliev updated IGNITE-19506: - Epic Link: IGNITE-19743 (was: IGNITE-19577) > Use data nodes from DistributionZoneManager with a causality token instead of > BaselineManager#nodes > --- > > Key: IGNITE-19506 > URL: https://issues.apache.org/jira/browse/IGNITE-19506 > Project: Ignite > Issue Type: Bug >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Major > Labels: ignite-3 > Time Spent: 1h > Remaining Estimate: 0h > > h3. *Motivation* > Need to use data nodes from DistributionZoneManager instead of > BaselineManager#nodes in: > # DistributionZoneRebalanceEngine#onUpdateReplicas > # TableManager#createAssignmentsSwitchRebalanceListener > We need to get data nodes consistently so we need to use revision of > configuration events and a meta storage events as causality token. Also need > to use VersionedValue to save data nodes with causality token. > Description of causality data nodes algorithm: > https://docs.google.com/document/d/1fq7HpHNF-hFEv8w8oIQCLAZObj3s5klrbQxuhsF7Dy0 > h3. *Definition of Done* > DistributionZoneRebalanceEngine#onUpdateReplicas and > TableManager#createAssignmentsSwitchRebalanceListener use data nodes from > DistributionZoneManager -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19506) Use data nodes from DistributionZoneManager with a causality token instead of BaselineManager#nodes
[ https://issues.apache.org/jira/browse/IGNITE-19506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Uttsel updated IGNITE-19506: --- Description: h3. *Motivation* Need to use data nodes from DistributionZoneManager instead of BaselineManager#nodes in: # DistributionZoneRebalanceEngine#onUpdateReplicas # TableManager#createAssignmentsSwitchRebalanceListener We need to get data nodes consistently so we need to use revision of configuration events and a meta storage events as causality token. Also need to use VersionedValue to save data nodes with causality token. Description of causality data nodes algorithm: https://docs.google.com/document/d/1fq7HpHNF-hFEv8w8oIQCLAZObj3s5klrbQxuhsF7Dy0 h3. *Definition of Done* DistributionZoneRebalanceEngine#onUpdateReplicas and TableManager#createAssignmentsSwitchRebalanceListener use data nodes from DistributionZoneManager was: h3. *Motivation* Need to use data nodes from DistributionZoneManager instead of BaselineManager#nodes in: # DistributionZoneRebalanceEngine#onUpdateReplicas # TableManager#createAssignmentsSwitchRebalanceListener We need to get data nodes consistently so we need to use revision of configuration events and a meta storage events as causality token. Also need to use VersionedValue to save data nodes with causality token. h3. *Definition of Done* DistributionZoneRebalanceEngine#onUpdateReplicas and TableManager#createAssignmentsSwitchRebalanceListener use data nodes from DistributionZoneManager > Use data nodes from DistributionZoneManager with a causality token instead of > BaselineManager#nodes > --- > > Key: IGNITE-19506 > URL: https://issues.apache.org/jira/browse/IGNITE-19506 > Project: Ignite > Issue Type: Bug >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Major > Labels: ignite-3 > Time Spent: 1h > Remaining Estimate: 0h > > h3. *Motivation* > Need to use data nodes from DistributionZoneManager instead of > BaselineManager#nodes in: > # DistributionZoneRebalanceEngine#onUpdateReplicas > # TableManager#createAssignmentsSwitchRebalanceListener > We need to get data nodes consistently so we need to use revision of > configuration events and a meta storage events as causality token. Also need > to use VersionedValue to save data nodes with causality token. > Description of causality data nodes algorithm: > https://docs.google.com/document/d/1fq7HpHNF-hFEv8w8oIQCLAZObj3s5klrbQxuhsF7Dy0 > h3. *Definition of Done* > DistributionZoneRebalanceEngine#onUpdateReplicas and > TableManager#createAssignmentsSwitchRebalanceListener use data nodes from > DistributionZoneManager -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19506) Use data nodes from DistributionZoneManager with a causality token instead of BaselineManager#nodes
[ https://issues.apache.org/jira/browse/IGNITE-19506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirza Aliev updated IGNITE-19506: - Epic Link: IGNITE-19577 (was: IGNITE-18528) > Use data nodes from DistributionZoneManager with a causality token instead of > BaselineManager#nodes > --- > > Key: IGNITE-19506 > URL: https://issues.apache.org/jira/browse/IGNITE-19506 > Project: Ignite > Issue Type: Bug >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Major > Labels: ignite-3 > Time Spent: 50m > Remaining Estimate: 0h > > h3. *Motivation* > Need to use data nodes from DistributionZoneManager instead of > BaselineManager#nodes in: > # DistributionZoneRebalanceEngine#onUpdateReplicas > # TableManager#createAssignmentsSwitchRebalanceListener > We need to get data nodes consistently so we need to use revision of > configuration events and a meta storage events as causality token. Also need > to use VersionedValue to save data nodes with causality token. > h3. *Definition of Done* > DistributionZoneRebalanceEngine#onUpdateReplicas and > TableManager#createAssignmentsSwitchRebalanceListener use data nodes from > DistributionZoneManager -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19506) Use data nodes from DistributionZoneManager with a causality token instead of BaselineManager#nodes
[ https://issues.apache.org/jira/browse/IGNITE-19506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Uttsel updated IGNITE-19506: --- Description: h3. *Motivation* Need to use data nodes from DistributionZoneManager instead of BaselineManager#nodes in: # DistributionZoneRebalanceEngine#onUpdateReplicas # TableManager#createAssignmentsSwitchRebalanceListener We need to get data nodes consistently so we need to use revision of configuration events and a meta storage events as causality token. Also need to use VersionedValue to save data nodes with causality token. h3. *Definition of Done* DistributionZoneRebalanceEngine#onUpdateReplicas and TableManager#createAssignmentsSwitchRebalanceListener use data nodes from DistributionZoneManager was: h3. *Motivation* Need to use data nodes from DistributionZoneManager instead of BaselineManager#nodes in: # DistributionZoneRebalanceEngine#onUpdateReplicas # TableManager#createAssignmentsSwitchRebalanceListener We need to get data nodes consistently so we need to use revision of configuration events and a meta storage events as causality token. Also need to use VersionedValue to save data nodes with causality token. h3. *Definition of Done* DistributionZoneRebalanceEngine#onUpdateReplicas and TableManager#createAssignmentsSwitchRebalanceListener use data nodes from DistributionZoneManager > Use data nodes from DistributionZoneManager with a causality token instead of > BaselineManager#nodes > --- > > Key: IGNITE-19506 > URL: https://issues.apache.org/jira/browse/IGNITE-19506 > Project: Ignite > Issue Type: Bug >Reporter: Sergey Uttsel >Priority: Major > Labels: ignite-3 > > h3. *Motivation* > Need to use data nodes from DistributionZoneManager instead of > BaselineManager#nodes in: > # DistributionZoneRebalanceEngine#onUpdateReplicas > # TableManager#createAssignmentsSwitchRebalanceListener > We need to get data nodes consistently so we need to use revision of > configuration events and a meta storage events as causality token. Also need > to use VersionedValue to save data nodes with causality token. > h3. *Definition of Done* > DistributionZoneRebalanceEngine#onUpdateReplicas and > TableManager#createAssignmentsSwitchRebalanceListener use data nodes from > DistributionZoneManager -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19506) Use data nodes from DistributionZoneManager with a causality token instead of BaselineManager#nodes
[ https://issues.apache.org/jira/browse/IGNITE-19506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Uttsel updated IGNITE-19506: --- Labels: ignite-3 (was: ) > Use data nodes from DistributionZoneManager with a causality token instead of > BaselineManager#nodes > --- > > Key: IGNITE-19506 > URL: https://issues.apache.org/jira/browse/IGNITE-19506 > Project: Ignite > Issue Type: Bug >Reporter: Sergey Uttsel >Priority: Major > Labels: ignite-3 > > h3. *Motivation* > Need to use data nodes from DistributionZoneManager instead of > BaselineManager#nodes in: > # DistributionZoneRebalanceEngine#onUpdateReplicas > # TableManager#createAssignmentsSwitchRebalanceListener > We need to get data nodes consistently so we need to use revision of > configuration events and a meta storage events as causality token. Also need > to use > VersionedValue to save data nodes with causality token. > h3. *Definition of Done* > DistributionZoneRebalanceEngine#onUpdateReplicas and > TableManager#createAssignmentsSwitchRebalanceListener use data nodes from > DistributionZoneManager -- This message was sent by Atlassian Jira (v8.20.10#820010)
