[ 
https://issues.apache.org/jira/browse/IGNITE-6579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16301632#comment-16301632
 ] 

Pavel Pereslegin edited comment on IGNITE-6579 at 12/25/17 7:50 AM:
--------------------------------------------------------------------

Hello [~v.pyatkov].

Could you provide more details about configuration and expected behavior.

I tried the following scenario and I believe it works fine.
# Set IGNITE_PDS_WAL_REBALANCE_THRESHOLD to 0 (default threshold = 500000).
# Start nodes A, B and C with PDS enabled (1 backup).
# Put data to cache.
# Stop node C.
# Put more data to cache.
# Rejoin node C to cluster (nodeId = 93206ec4-0b0a-4c91-bb55-79b05f100002).
# Observing messages from coordinator about outdated update counters 
(haveHistory=true):

{noformat}
Partition has been scheduled for rebalancing due to outdated update counter 
[nodeId=93206ec4-0b0a-4c91-bb55-79b05f100002, cacheOrGroupName=default, 
partId=0, haveHistory=true]
Partition has been scheduled for rebalancing due to outdated update counter 
[nodeId=93206ec4-0b0a-4c91-bb55-79b05f100002, cacheOrGroupName=default, 
partId=1, haveHistory=true]
Partition has been scheduled for rebalancing due to outdated update counter 
[nodeId=93206ec4-0b0a-4c91-bb55-79b05f100002, cacheOrGroupName=default, 
partId=4, haveHistory=true]
...
{noformat}


was (Author: xtern):
Hello [~v.pyatkov].

Could you provide more details about your configuration and behavior that you 
expect to see (or how to reproduce this bug).

I tried following scenario and I believe it works well.
# Set IGNITE_PDS_WAL_REBALANCE_THRESHOLD to 0 (default threshold = 500000).
# Start nodes A, B and C with PDS enabled (1 backup).
# Add data to cache.
# Stop node C.
# Add more data to cache.
# Rejoin node C to cluster (nodeId = 93206ec4-0b0a-4c91-bb55-79b05f100002).
# Observing messages from coordinator about outdated update counters 
(haveHistory=true):

{noformat}
Partition has been scheduled for rebalancing due to outdated update counter 
[nodeId=93206ec4-0b0a-4c91-bb55-79b05f100002, cacheOrGroupName=default, 
partId=0, haveHistory=true]
Partition has been scheduled for rebalancing due to outdated update counter 
[nodeId=93206ec4-0b0a-4c91-bb55-79b05f100002, cacheOrGroupName=default, 
partId=1, haveHistory=true]
Partition has been scheduled for rebalancing due to outdated update counter 
[nodeId=93206ec4-0b0a-4c91-bb55-79b05f100002, cacheOrGroupName=default, 
partId=4, haveHistory=true]
...
{noformat}

> 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
>
> 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
(v6.4.14#64029)

Reply via email to