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

Ilya Shishkov edited comment on IGNITE-17865 at 10/13/22 8:15 AM:
------------------------------------------------------------------

[~slava.koptilin], hi!

I agree, that blowing up of logs is not a god idea, but are there any practical 
results, when such optimization can significantly reduce size of message and 
logs?
As I see, most of time lists of partitions in these messages does 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.


was (Author: shishkovilja):
[~slava.koptilin], hi!

I understand, that blowing up of logs is not a god idea, but are there any 
practical results, when such optimization can significantly reduce size of 
message and logs?
As I see, most of time lists of partitions in these messages does not form a 
continuous sequence, and even if so, only 2, and less often 3 and more 
partitions are forms continuous sequence. And for two partitions real economy 
is a whitespace symbol.

> 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)

Reply via email to