[
https://issues.apache.org/jira/browse/IGNITE-17865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-17865:
-----------------------------------
Description:
When you need to analyze cases of partitions inconsistency, full list of
partitions is needed, but there is an optimization which replaces list of
consecutive partitions with ranges. So, as you can see below, we can not find
partition 2 by simple text search:
{quote}
2021-08-11 23:12:11.338 [WARN
][sys-#213][org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl]
Partitions have been scheduled for rebalancing due to outdated update counter
[grp=group, readyTopVer=AffinityTopologyVersion [topVer=33, minorTopVer=0],
topVer=AffinityTopologyVersion [topVer=33, minorTopVer=0],
nodeId=8e05997a-4ff7-4fdb-9480-cfbcefa8bbf5,
partsFull=[{color:red}*1-3*{color}, ...], partsHistorical=[]]
{quote}
{quote}
2021-08-11 23:12:11.338 [WARN
][sys-#213][org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture]
Partitions weren't present in any history reservation: [[[grp=grp2
part=[[{color:red}*1-3*{color}]]]
{quote}
We need to remove this optimization, because it can lead to mistakes in logs
analysis.
was:
When you need to analyze cases of partitions inconsistency, full list of
partitions is needed, but there is an optimization which replaces list of
consecutive partitions with ranges. So, as you can see below, we can not find
partition 2 by simple text search:
{quote}
2021-08-11 23:12:11.338 [WARN
][sys-#213][org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl]
Partitions have been scheduled for rebalancing due to outdated update counter
[grp=group, readyTopVer=AffinityTopologyVersion [topVer=33, minorTopVer=0],
topVer=AffinityTopologyVersion [topVer=33, minorTopVer=0],
nodeId=8e05997a-4ff7-4fdb-9480-cfbcefa8bbf5,
partsFull=[*{color:red}1-3{color}*, ...], partsHistorical=[]]
{quote}
{quote}
2021-08-11 23:12:11.338 [WARN
][sys-#213][org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture]
Partitions weren't present in any history reservation: [[[grp=grp2
part=[[*{color:red}1-3{color}*]]]
{quote}
We need to remove this optimization, because it can lead to mistakes in logs
analysis.
> Disable partition ranges in log messages about rebalance or PME
> ---------------------------------------------------------------
>
> Key: IGNITE-17865
> URL: https://issues.apache.org/jira/browse/IGNITE-17865
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Ilya Shishkov
> Priority: Minor
> Labels: ise
>
> When you need to analyze cases of partitions inconsistency, full list of
> partitions is needed, but there is an optimization which replaces list of
> consecutive partitions with ranges. So, as you can see below, we can not find
> partition 2 by simple text search:
> {quote}
> 2021-08-11 23:12:11.338 [WARN
> ][sys-#213][org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl]
> Partitions have been scheduled for rebalancing due to outdated update
> counter [grp=group, readyTopVer=AffinityTopologyVersion [topVer=33,
> minorTopVer=0], topVer=AffinityTopologyVersion [topVer=33, minorTopVer=0],
> nodeId=8e05997a-4ff7-4fdb-9480-cfbcefa8bbf5,
> partsFull=[{color:red}*1-3*{color}, ...], partsHistorical=[]]
> {quote}
> {quote}
> 2021-08-11 23:12:11.338 [WARN
> ][sys-#213][org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture]
> Partitions weren't present in any history reservation: [[[grp=grp2
> part=[[{color:red}*1-3*{color}]]]
> {quote}
> We need to remove this optimization, because it can lead to mistakes in logs
> analysis.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
