You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Evgenii Zhuravlev (JIRA)" <ji...@apache.org> on 2019/01/24 01:21:00 UTC
[jira] [Updated] (IGNITE-11052) Add documentation for "failed to
wait for partition map exchange" message
[ https://issues.apache.org/jira/browse/IGNITE-11052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Evgenii Zhuravlev updated IGNITE-11052:
---------------------------------------
Description:
We should describe why this message could be seen in logs and how to debug the real problem that caused this message.
This message can be printed in the case when cluster trying to change topology version when some of the operations still running on the previous topology version. It could be either long running operations which could finish successfully after a while or deadlock(or some other operations, that won't be able to finish by some reason)
Here are some examples on the user list:
http://apache-ignite-users.70518.x6.nabble.com/Failed-to-wait-for-initial-partition-map-exchange-td6252i20.html
http://apache-ignite-users.70518.x6.nabble.com/Large-durable-caches-td20097i20.html
http://apache-ignite-users.70518.x6.nabble.com/Cache-operations-hanging-for-a-minute-when-one-of-server-nodes-goes-down-td21964.html
was:We should describe why this message could be seen in logs and how to debug the real problem that caused this message.
> Add documentation for "failed to wait for partition map exchange" message
> -------------------------------------------------------------------------
>
> Key: IGNITE-11052
> URL: https://issues.apache.org/jira/browse/IGNITE-11052
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
> Reporter: Evgenii Zhuravlev
> Assignee: Denis Magda
> Priority: Major
>
> We should describe why this message could be seen in logs and how to debug the real problem that caused this message.
> This message can be printed in the case when cluster trying to change topology version when some of the operations still running on the previous topology version. It could be either long running operations which could finish successfully after a while or deadlock(or some other operations, that won't be able to finish by some reason)
> Here are some examples on the user list:
> http://apache-ignite-users.70518.x6.nabble.com/Failed-to-wait-for-initial-partition-map-exchange-td6252i20.html
> http://apache-ignite-users.70518.x6.nabble.com/Large-durable-caches-td20097i20.html
> http://apache-ignite-users.70518.x6.nabble.com/Cache-operations-hanging-for-a-minute-when-one-of-server-nodes-goes-down-td21964.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)