[jira] [Updated] (IGNITE-2779) BinaryMarshaller caches must be cleaned during client reconnect.
[
https://issues.apache.org/jira/browse/IGNITE-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-2779:
Fix Version/s: (was: 2.1)
2.2
> BinaryMarshaller caches must be cleaned during client reconnect.
>
>
> Key: IGNITE-2779
> URL: https://issues.apache.org/jira/browse/IGNITE-2779
> Project: Ignite
> Issue Type: Task
> Components: cache, general
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
> Labels: community
> Fix For: 2.2
>
> Attachments: IgniteProblemTest.java
>
>
> The problem is originally reported by Vinay Sharma here:
> http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarted-server-nodes-Getting-exception-td3064.html#none
> *Root cause*:
> When client is reconnected to topology after full topology restart (i.e. all
> server nodes were down), it doesn't re-send binary metadata to topology. As a
> result, {{BinaryMarshaller}} exception occurs.
> *Steps to reproduce*
> Run attached code.
> *Proposed solution*
> Clean cached binary metadata during re-connect.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-2779) BinaryMarshaller caches must be cleaned during client reconnect.
[
https://issues.apache.org/jira/browse/IGNITE-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-2779:
Fix Version/s: (was: 2.0)
2.1
> BinaryMarshaller caches must be cleaned during client reconnect.
>
>
> Key: IGNITE-2779
> URL: https://issues.apache.org/jira/browse/IGNITE-2779
> Project: Ignite
> Issue Type: Task
> Components: cache, general
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
> Labels: community
> Fix For: 2.1
>
> Attachments: IgniteProblemTest.java
>
>
> The problem is originally reported by Vinay Sharma here:
> http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarted-server-nodes-Getting-exception-td3064.html#none
> *Root cause*:
> When client is reconnected to topology after full topology restart (i.e. all
> server nodes were down), it doesn't re-send binary metadata to topology. As a
> result, {{BinaryMarshaller}} exception occurs.
> *Steps to reproduce*
> Run attached code.
> *Proposed solution*
> Clean cached binary metadata during re-connect.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-2779) BinaryMarshaller caches must be cleaned during client reconnect.
[
https://issues.apache.org/jira/browse/IGNITE-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-2779:
Labels: community (was: community important)
> BinaryMarshaller caches must be cleaned during client reconnect.
>
>
> Key: IGNITE-2779
> URL: https://issues.apache.org/jira/browse/IGNITE-2779
> Project: Ignite
> Issue Type: Task
> Components: cache, general
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
> Labels: community
> Fix For: 2.0
>
> Attachments: IgniteProblemTest.java
>
>
> The problem is originally reported by Vinay Sharma here:
> http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarted-server-nodes-Getting-exception-td3064.html#none
> *Root cause*:
> When client is reconnected to topology after full topology restart (i.e. all
> server nodes were down), it doesn't re-send binary metadata to topology. As a
> result, {{BinaryMarshaller}} exception occurs.
> *Steps to reproduce*
> Run attached code.
> *Proposed solution*
> Clean cached binary metadata during re-connect.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-2779) BinaryMarshaller caches must be cleaned during client reconnect.
[
https://issues.apache.org/jira/browse/IGNITE-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-2779:
Priority: Major (was: Critical)
> BinaryMarshaller caches must be cleaned during client reconnect.
>
>
> Key: IGNITE-2779
> URL: https://issues.apache.org/jira/browse/IGNITE-2779
> Project: Ignite
> Issue Type: Task
> Components: cache, general
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
> Labels: community, important
> Fix For: 2.0
>
> Attachments: IgniteProblemTest.java
>
>
> The problem is originally reported by Vinay Sharma here:
> http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarted-server-nodes-Getting-exception-td3064.html#none
> *Root cause*:
> When client is reconnected to topology after full topology restart (i.e. all
> server nodes were down), it doesn't re-send binary metadata to topology. As a
> result, {{BinaryMarshaller}} exception occurs.
> *Steps to reproduce*
> Run attached code.
> *Proposed solution*
> Clean cached binary metadata during re-connect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2779) BinaryMarshaller caches must be cleaned during client reconnect.
[
https://issues.apache.org/jira/browse/IGNITE-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-2779:
Fix Version/s: (was: 1.8)
2.0
> BinaryMarshaller caches must be cleaned during client reconnect.
>
>
> Key: IGNITE-2779
> URL: https://issues.apache.org/jira/browse/IGNITE-2779
> Project: Ignite
> Issue Type: Task
> Components: cache, general
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Priority: Critical
> Labels: community, important
> Fix For: 2.0
>
> Attachments: IgniteProblemTest.java
>
>
> The problem is originally reported by Vinay Sharma here:
> http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarted-server-nodes-Getting-exception-td3064.html#none
> *Root cause*:
> When client is reconnected to topology after full topology restart (i.e. all
> server nodes were down), it doesn't re-send binary metadata to topology. As a
> result, {{BinaryMarshaller}} exception occurs.
> *Steps to reproduce*
> Run attached code.
> *Proposed solution*
> Clean cached binary metadata during re-connect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2779) BinaryMarshaller caches must be cleaned during client reconnect.
[
https://issues.apache.org/jira/browse/IGNITE-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-2779:
Fix Version/s: (was: 1.6)
1.7
> BinaryMarshaller caches must be cleaned during client reconnect.
>
>
> Key: IGNITE-2779
> URL: https://issues.apache.org/jira/browse/IGNITE-2779
> Project: Ignite
> Issue Type: Task
> Components: cache, general
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Priority: Critical
> Labels: community, important
> Fix For: 1.7
>
> Attachments: IgniteProblemTest.java
>
>
> The problem is originally reported by Vinay Sharma here:
> http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarted-server-nodes-Getting-exception-td3064.html#none
> *Root cause*:
> When client is reconnected to topology after full topology restart (i.e. all
> server nodes were down), it doesn't re-send binary metadata to topology. As a
> result, {{BinaryMarshaller}} exception occurs.
> *Steps to reproduce*
> Run attached code.
> *Proposed solution*
> Clean cached binary metadata during re-connect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2779) BinaryMarshaller caches must be cleaned during client reconnect.
[
https://issues.apache.org/jira/browse/IGNITE-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-2779:
Labels: community (was: )
> BinaryMarshaller caches must be cleaned during client reconnect.
>
>
> Key: IGNITE-2779
> URL: https://issues.apache.org/jira/browse/IGNITE-2779
> Project: Ignite
> Issue Type: Task
> Components: cache, general
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Priority: Critical
> Labels: community, important
> Fix For: 1.6
>
> Attachments: IgniteProblemTest.java
>
>
> The problem is originally reported by Vinay Sharma here:
> http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarted-server-nodes-Getting-exception-td3064.html#none
> *Root cause*:
> When client is reconnected to topology after full topology restart (i.e. all
> server nodes were down), it doesn't re-send binary metadata to topology. As a
> result, {{BinaryMarshaller}} exception occurs.
> *Steps to reproduce*
> Run attached code.
> *Proposed solution*
> Clean cached binary metadata during re-connect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2779) BinaryMarshaller caches must be cleaned during client reconnect.
[
https://issues.apache.org/jira/browse/IGNITE-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-2779:
Labels: community important (was: community)
> BinaryMarshaller caches must be cleaned during client reconnect.
>
>
> Key: IGNITE-2779
> URL: https://issues.apache.org/jira/browse/IGNITE-2779
> Project: Ignite
> Issue Type: Task
> Components: cache, general
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Priority: Critical
> Labels: community, important
> Fix For: 1.6
>
> Attachments: IgniteProblemTest.java
>
>
> The problem is originally reported by Vinay Sharma here:
> http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarted-server-nodes-Getting-exception-td3064.html#none
> *Root cause*:
> When client is reconnected to topology after full topology restart (i.e. all
> server nodes were down), it doesn't re-send binary metadata to topology. As a
> result, {{BinaryMarshaller}} exception occurs.
> *Steps to reproduce*
> Run attached code.
> *Proposed solution*
> Clean cached binary metadata during re-connect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2779) BinaryMarshaller caches must be cleaned during client reconnect.
[
https://issues.apache.org/jira/browse/IGNITE-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-2779:
Attachment: IgniteProblemTest.java
> BinaryMarshaller caches must be cleaned during client reconnect.
>
>
> Key: IGNITE-2779
> URL: https://issues.apache.org/jira/browse/IGNITE-2779
> Project: Ignite
> Issue Type: Task
> Components: cache, general
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.6
>
> Attachments: IgniteProblemTest.java
>
>
> The problem is originally reported by Vinay Sharma here:
> http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarted-server-nodes-Getting-exception-td3064.html#none
> *Root cause*:
> When client is reconnected to topology after full topology restart (i.e. all
> server nodes were down), it doesn't re-send binary metadata to topology. As a
> result, {{BinaryMarshaller}} exception occurs.
> *Steps to reproduce*
> Run attached code.
> *Proposed solution*
> Clean cached binary metadata during re-connect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
