You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ignite.apache.org by "sanpwc (via GitHub)" <gi...@apache.org> on 2023/02/14 09:59:15 UTC
[GitHub] [ignite-3] sanpwc commented on a diff in pull request #1655: IGNITE-18737 Tests from ItIgniteNodeRestartTest became flaky
sanpwc commented on code in PR #1655:
URL: https://github.com/apache/ignite-3/pull/1655#discussion_r1105560862
##########
modules/table/src/main/java/org/apache/ignite/internal/table/distributed/TableManager.java:
##########
@@ -1863,23 +1863,36 @@ public void onUpdate(WatchEvent evt) {
if (zoneId == tableZoneId) {
TableConfiguration tableCfg = tables.get(tableView.name());
+ byte[] assignmentsBytes = ((ExtendedTableConfiguration) tableCfg).assignments().value();
+
+ List<Set<Assignment>> tableAssignments = ByteUtils.fromBytes(assignmentsBytes);
+
for (int part = 0; part < tableView.partitions(); part++) {
UUID tableId = ((ExtendedTableConfiguration) tableCfg).id().value();
TablePartitionId replicaGrpId = new TablePartitionId(tableId, part);
- int partId = part;
+ int replicas = tableView.replicas();
- updatePendingAssignmentsKeys(
Review Comment:
Besides updating pending assignments inside updatePendingAssignmentsKeys we also update `partition.change.trigger.revision `. Should we update it even if won't update the assignments themselves?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@ignite.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org