You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Kukushkin (JIRA)" <ji...@apache.org> on 2017/06/29 18:17:05 UTC

[jira] [Commented] (IGNITE-4901) Decrease logging level for DataStremer retry

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

Alexey Kukushkin commented on IGNITE-4901:
------------------------------------------

Presently when DataStreamer is flushing data and cluster topology changes, the DataStreamer would output an ERROR message to the console and retry flushing the data with the latest topology. 

We have this IGNITE-4901 issue asking to decrease logging level since a topology change is normal and DataStreamer reliably handles it.

In addition to setting the log level to INFO, I suggest we change Ignite to fail to update the cache only if MAJOR topology version changed (another node joined/left) since minor version change (registering/unregistering another cache) does not impact updating the cache unless we delete the cache-in-use but the latter error is handled differently anyway.

Please let me know if anyone has objections or comments. Otherwise I will submit this solution.


> Decrease logging level for DataStremer retry 
> ---------------------------------------------
>
>                 Key: IGNITE-4901
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4901
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>    Affects Versions: 1.9
>            Reporter: Nikolay Tikhonov
>            Assignee: Alexey Kukushkin
>            Priority: Trivial
>
> When topology are changed DataStreame log the following error message which confused users. Need to decrease logging level for this case.
> {noformat}
> ERROR  Failed to execute compound future reducer: GridCompoundFuture [...] class org.apache.ignite.IgniteCheckedException: DataStreamer request failed [node=9d405934-eb78-4452-a3a8-fc44c3c61e76] 
> 	at org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.onResponse(DataStreamerImpl.java:1777) 
> 	at org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$3.onMessage(DataStreamerImpl.java:335) 
> 	at org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1080) 
> 	at org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:708) 
> 	at org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:101) 
> 	at org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:671) 
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
> 	at java.lang.Thread.run(Thread.java:745) 
> Caused by: class org.apache.ignite.IgniteCheckedException: DataStreamer will retry data transfer at stable topology [...] 
> 	at org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.localUpdate(DataStreamProcessor.java:337) 
> 	at org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:297) 
> 	at org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:56) 
> 	at org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:86) 
> 	... 7 more 
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)