You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/05/29 13:26:00 UTC
[jira] [Commented] (IGNITE-8636) Debug logging improvements for
Partition Map Exchange process
[ https://issues.apache.org/jira/browse/IGNITE-8636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16493522#comment-16493522 ]
ASF GitHub Bot commented on IGNITE-8636:
----------------------------------------
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/4087
IGNITE-8636 debug logging for client join scenario
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8636
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4087.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 #4087
----
commit a4f650a870f23314e0ce0fdedf5e36627887bfe2
Author: Sergey Chugunov <se...@...>
Date: 2018-05-29T12:05:12Z
IGNITE-8636 debug logging for client join scenario
----
> Debug logging improvements for Partition Map Exchange process
> -------------------------------------------------------------
>
> Key: IGNITE-8636
> URL: https://issues.apache.org/jira/browse/IGNITE-8636
> Project: Ignite
> Issue Type: Improvement
> Affects Versions: 2.5
> Reporter: Sergey Chugunov
> Assignee: Sergey Chugunov
> Priority: Major
> Fix For: 2.6
>
>
> Debug logging in ExchangeManager and ExchangeFuture lacks important scenario of client joining topology.
> All we see is client sending GridDhtPartitionsSingleMessage and coordinator receiving this message.
> If client doesn't receive GridDhtPartitionsFullMessage for its SingleMessage there is no information in client or server logs at which moment something went wrong.
> Debug logging of the scenario should be improved, all important steps should be covered with informative messages in logs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)