[
https://issues.apache.org/jira/browse/IGNITE-17865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17620468#comment-17620468
]
Vyacheslav Koptilin commented on IGNITE-17865:
----------------------------------------------
Hello [~shishkovilja],
??As I see, most of time lists of partitions in these messages do not form a
continuous sequence, and even if so, only 2, and less often 3 and more
partitions form continuous sequence. And for two partitions real economy is a
whitespace symbol.??
Let's try to compare the output for the following scenario:
{noformat}
1.
fullPartitions=[4-5, 260-261, 500-501]
fullPartitions=[4, 5, 260, 261, 500, 501] The difference is not so big
for the case when a sequence size is equal to 2
2.
fullPartitions=[1-3, 37, 50-52, 101, 999-1001]
fullPartitions=[1, 2, 3, 37, 50, 51, 52, 101, 999, 1000, 1001] In this
case, the optimized output looks better than non optimized.
{noformat}
You need to take into account, that this output will be printed for each cache,
which should be rebalanced, and each supplier node.
All in all, I don't want to say: "please stop, you should not turn off this
optimization". :) It's up to you.
It seems to me, that even a small optimization is more useful than not having
it at all.
> 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, newbie
>
> 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)
