[
https://issues.apache.org/jira/browse/IGNITE-17865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623070#comment-17623070
]
Ilya Shishkov edited comment on IGNITE-17865 at 10/24/22 9:36 AM:
------------------------------------------------------------------
Hello [~slava.koptilin] ,
{quote}
In this case, the optimized output looks better than non optimized.
{quote}
My point is that we should provide end user possibility use simple text search,
by means of regular expression or not it does not matter. For now we can
suggest only to reinvent the wheel by creating a range parsing function.
But, may be I'm wrong and solution (regex or other) is too obvious and simple?
{quote}
It seems to me, that even a small optimization is more useful than not having
it at all.
{quote}
We can add extra system property to turning on/of the optimization? WDYT?
was (Author: shishkovilja):
Hello [~slava.koptilin] ,
{quote}
In this case, the optimized output looks better than non optimized.
{quote}
My point is that we should provide end user possibility use simple text search,
by means of regular expression or not it does not matter. For now we can
suggest only to reinvent the wheel by creating a range parsing function.
But, may be I'm wrong and solution (regex or other) is too obvious and simple?
> 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)
