[jira] [Comment Edited] (IGNITE-5869) Unexpected timeout exception while client connected with different BinaryConfiguration compactFooter param.

["Dmitriy Setrakyan (JIRA)" <ji...@apache.org>]

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

Dmitriy Setrakyan edited comment on IGNITE-5869 at 7/31/17 7:33 AM:
--------------------------------------------------------------------

Is Ignite supposed to work with different compactFooter configurations in the cluster? If not, why do we even allow for such clients to connect?


was (Author: dsetrakyan):
Is Ignite supposed to work with different compactFooter configurations in the cluster? If not, why do we even allow for such client to connect?

> Unexpected timeout exception while client connected with different BinaryConfiguration compactFooter param.
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-5869
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5869
>             Project: Ignite
>          Issue Type: Bug
>          Components: clients
>    Affects Versions: 2.0
>            Reporter: Stanilovsky Evgeny
>            Assignee: Stanilovsky Evgeny
>         Attachments: TcpClientDiscoveryMarshallerCheckSelfTest.java
>
>
> While client connecting with different from cluster BinaryConfiguration::setCompactFooter param, instead of expecting: "configuration is not equal" exception catch: Join process timed out exception.



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