[
https://issues.apache.org/jira/browse/IGNITE-6579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16328816#comment-16328816
]
Pavel Pereslegin edited comment on IGNITE-6579 at 2/19/18 12:59 PM:
--------------------------------------------------------------------
Hello, [~v.pyatkov].
I agree, but since coordinator doesn't have information about non local
partition sizes we can't simply point to this restriction here, at least
without some irrelevant changes to existing partition exchange procedure.
To improve understanding, may be, we can add debug message on nodes where WAL
history is being reserved for exchange (in case partition size too small for
partial rebalancing)?
was (Author: xtern):
Hello, [~v.pyatkov].
I agreed, but since coordinator doesn't have information about non local
partition sizes we can't simply point to this restriction here, at least
without some irrelevant changes to existing partition exchange procedure.
To improve understanding, may be, we can add debug message on nodes where WAL
history is being reserved for exchange (in case partition size too small for
partial rebalancing)?
> WAL history does not used when node returns to cluster again
> ------------------------------------------------------------
>
> Key: IGNITE-6579
> URL: https://issues.apache.org/jira/browse/IGNITE-6579
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Reporter: Vladislav Pyatkov
> Priority: Major
>
> When I have set big enough value to "WAL history size" and stop node on 20
> minutes, I got the message from coordinator (order=1):
> {noformat}
> 2017-10-06 15:46:33.429 [WARN
> ][sys-#10740%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.GridDhtPartitionTopologyImpl]
> Partition has been scheduled for rebalancing due to outdated update counter
> [nodeId=e51a1db2-f49b-44a9-b122-adde4016d9e7,
> cacheOrGroupName=CACHEGROUP_PARTICLE_DServiceZone, partId=2424,
> haveHistory=false]
> 2017-10-06 15:46:33.429 [WARN
> ][sys-#10740%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.GridDhtPartitionTopologyImpl]
> Partition has been scheduled for rebalancing due to outdated update counter
> [nodeId=e51a1db2-f49b-44a9-b122-adde4016d9e7,
> cacheOrGroupName=CACHEGROUP_PARTICLE_DServiceZone, partId=2427,
> haveHistory=false]
> 2017-10-06 15:46:33.429 [WARN
> ][sys-#10740%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.GridDhtPartitionTopologyImpl]
> Partition has been scheduled for rebalancing due to outdated update counter
> [nodeId=e51a1db2-f49b-44a9-b122-adde4016d9e7,
> cacheOrGroupName=CACHEGROUP_PARTICLE_DServiceZone, partId=2426,
> haveHistory=false]
> {noformat}
> after start node again.
> I think, history size should be enough, but I see it is not by logs
> (haveHistory=false).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
