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

ASF GitHub Bot commented on IGNITE-10295:
-----------------------------------------

GitHub user voropava opened a pull request:

    https://github.com/apache/ignite/pull/5413

    IGNITE-10295 Added info logging for long connection establish methods…

    …, removed useless logging of Sending Full Message.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-10295

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/5413.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #5413
    
----
commit da856f3883c76276eb034cfbea70a7beb85ea8d8
Author: Pavel Voronkin <pvoronkin@...>
Date:   2018-11-09T12:00:03Z

    IGNITE-10295 Added info logging for long connection establish methods, 
removed useless logging of Sending Full Message.

----


> Rework Sending Full Message logging.
> ------------------------------------
>
>                 Key: IGNITE-10295
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10295
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Pavel Voronkin
>            Assignee: Pavel Voronkin
>            Priority: Major
>
> [16:33:34,410][INFO][sys-#122][GridDhtPartitionsExchangeFuture] Sending Full 
> Message performed in 0 ms.
> [16:33:34,410][INFO][sys-#122][GridDhtPartitionsExchangeFuture] Sending Full 
> Message to all nodes performed in 0 ms.
> [16:33:32,993][INFO][exchange-worker-#66][GridDhtPartitionsExchangeFuture] 
> Sending Single Message performed in 150 ms.
>  
> For varying number of caches, server nodes or number of partitions, reported 
> single message time change respectively, but reported full message time 
> always printed as 0 or 1 ms. Seems that it is calculated incorrectly, cause 
> of async send of message.
> The most we spend in this method is actually open connection on send()
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to