ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Pereslegin (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (IGNITE-6579) WAL history does not used when node returns to cluster again
Date Mon, 25 Dec 2017 12:08:00 GMT

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

Pavel Pereslegin edited comment on IGNITE-6579 at 12/25/17 12:07 PM:
---------------------------------------------------------------------

Hello [~v.pyatkov],

I retested with the following scenario:

# Set IGNITE_PDS_WAL_REBALANCE_THRESHOLD to 10000.
# Start nodes A, B and C with one replicated cache (RendezvousAffinityFunction with 10 partitions).
# Put 100000 values to cache (10000 keys per partition).
# Stop node C.
# Put 3000 values to cache (10300 keys per partition).
# Rejoin node C (nodeId = 606c6f4d-c314-4345-8b6d-cc3f37900002).
# Observing messages from coordinator (haveHistory=true).

{noformat}
Partition has been scheduled for rebalancing due to outdated update counter [nodeId=606c6f4d-c314-4345-8b6d-cc3f37900002,
cacheOrGroupName=default, partId=0, haveHistory=true]
Partition has been scheduled for rebalancing due to outdated update counter [nodeId=606c6f4d-c314-4345-8b6d-cc3f37900002,
cacheOrGroupName=default, partId=1, haveHistory=true]
Partition has been scheduled for rebalancing due to outdated update counter [nodeId=606c6f4d-c314-4345-8b6d-cc3f37900002,
cacheOrGroupName=default, partId=2, haveHistory=true]
Partition has been scheduled for rebalancing due to outdated update counter [nodeId=606c6f4d-c314-4345-8b6d-cc3f37900002,
cacheOrGroupName=default, partId=3, haveHistory=true]
Partition has been scheduled for rebalancing due to outdated update counter [nodeId=606c6f4d-c314-4345-8b6d-cc3f37900002,
cacheOrGroupName=default, partId=4, haveHistory=true]
Partition has been scheduled for rebalancing due to outdated update counter [nodeId=606c6f4d-c314-4345-8b6d-cc3f37900002,
cacheOrGroupName=default, partId=5, haveHistory=true]
Partition has been scheduled for rebalancing due to outdated update counter [nodeId=606c6f4d-c314-4345-8b6d-cc3f37900002,
cacheOrGroupName=default, partId=6, haveHistory=true]
Partition has been scheduled for rebalancing due to outdated update counter [nodeId=606c6f4d-c314-4345-8b6d-cc3f37900002,
cacheOrGroupName=default, partId=7, haveHistory=true]
Partition has been scheduled for rebalancing due to outdated update counter [nodeId=606c6f4d-c314-4345-8b6d-cc3f37900002,
cacheOrGroupName=default, partId=8, haveHistory=true]
Partition has been scheduled for rebalancing due to outdated update counter [nodeId=606c6f4d-c314-4345-8b6d-cc3f37900002,
cacheOrGroupName=default, partId=9, haveHistory=true]
{noformat}

If I set IGNITE_PDS_WAL_REBALANCE_THRESHOLD larger than the partition size (10301 for example)
- WAL history is not used.
{noformat}
Partition has been scheduled for rebalancing due to outdated update counter [nodeId=606c6f4d-c314-4345-8b6d-cc3f37900002,
cacheOrGroupName=default, partId=0, haveHistory=false]
Partition has been scheduled for rebalancing due to outdated update counter [nodeId=606c6f4d-c314-4345-8b6d-cc3f37900002,
cacheOrGroupName=default, partId=1, haveHistory=false]
...{noformat}


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

I tried the following scenario:

# Set JVM option -DIGNITE_PDS_WAL_REBALANCE_THRESHOLD=10000.
# Start nodes A, B and C with one replicated cache (no backups, RendezvousAffinityFunction
with 10 partitions).
# Put 100000 values to cache (10000 keys per partition).
# Stop node C.
# Put 3000 values to cache (10300 keys per partition).
# Rejoin node C (nodeId = 606c6f4d-c314-4345-8b6d-cc3f37900002).
# Observing messages from coordinator (haveHistory=true).

{noformat}
[GridDhtPartitionTopologyImpl] Partition has been scheduled for rebalancing due to outdated
update counter [nodeId=606c6f4d-c314-4345-8b6d-cc3f37900002, cacheOrGroupName=default, partId=0,
haveHistory=true]
[GridDhtPartitionTopologyImpl] Partition has been scheduled for rebalancing due to outdated
update counter [nodeId=606c6f4d-c314-4345-8b6d-cc3f37900002, cacheOrGroupName=default, partId=1,
haveHistory=true]
[GridDhtPartitionTopologyImpl] Partition has been scheduled for rebalancing due to outdated
update counter [nodeId=606c6f4d-c314-4345-8b6d-cc3f37900002, cacheOrGroupName=default, partId=2,
haveHistory=true]
[GridDhtPartitionTopologyImpl] Partition has been scheduled for rebalancing due to outdated
update counter [nodeId=606c6f4d-c314-4345-8b6d-cc3f37900002, cacheOrGroupName=default, partId=3,
haveHistory=true]
[GridDhtPartitionTopologyImpl] Partition has been scheduled for rebalancing due to outdated
update counter [nodeId=606c6f4d-c314-4345-8b6d-cc3f37900002, cacheOrGroupName=default, partId=4,
haveHistory=true]
[GridDhtPartitionTopologyImpl] Partition has been scheduled for rebalancing due to outdated
update counter [nodeId=606c6f4d-c314-4345-8b6d-cc3f37900002, cacheOrGroupName=default, partId=5,
haveHistory=true]
[GridDhtPartitionTopologyImpl] Partition has been scheduled for rebalancing due to outdated
update counter [nodeId=606c6f4d-c314-4345-8b6d-cc3f37900002, cacheOrGroupName=default, partId=6,
haveHistory=true]
[GridDhtPartitionTopologyImpl] Partition has been scheduled for rebalancing due to outdated
update counter [nodeId=606c6f4d-c314-4345-8b6d-cc3f37900002, cacheOrGroupName=default, partId=7,
haveHistory=true]
[GridDhtPartitionTopologyImpl] Partition has been scheduled for rebalancing due to outdated
update counter [nodeId=606c6f4d-c314-4345-8b6d-cc3f37900002, cacheOrGroupName=default, partId=8,
haveHistory=true]
[GridDhtPartitionTopologyImpl] Partition has been scheduled for rebalancing due to outdated
update counter [nodeId=606c6f4d-c314-4345-8b6d-cc3f37900002, cacheOrGroupName=default, partId=9,
haveHistory=true]
{noformat}

If I set IGNITE_PDS_WAL_REBALANCE_THRESHOLD larger than the partition size (10301 for example)
- WAL history is not used.
{noformat}
Partition has been scheduled for rebalancing due to outdated update counter [nodeId=606c6f4d-c314-4345-8b6d-cc3f37900002,
cacheOrGroupName=default, partId=0, haveHistory=false]
Partition has been scheduled for rebalancing due to outdated update counter [nodeId=606c6f4d-c314-4345-8b6d-cc3f37900002,
cacheOrGroupName=default, partId=1, haveHistory=false]
...{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)

Mime
View raw message