Hi,
If you think what dedlock there, you can increase
IGNITE_LONG_OPERATIONS_DUMP_TIMEOUT (through jvm system properties) and
networkTimeout (through Ignite configuration xml) to several minutes.
-DIGNITE_LONG_OPERATIONS_DUMP_TIMEOUT=300000
<bean class="org.apache.ignite.configuration.IgniteConfiguration">
<property name="networkTimeout" value="150000" />
On Thu, Aug 18, 2016 at 12:22 PM, Jason <fqy...@outlook.com> wrote:
> Thanks Vladislav.
>
> Will try to reproduce this issue again, and seems that this only happens in
> a big cluster.
>
> BTW, after the new node joins, and when it tries to do partition map
> exchange, seems that there's deadlock.
> In some nodes, "Failed to wait for partition map ..." and other nodes,
> "Failed to wait for partition eviction ...".
>
> And I've attached the detailed log for all 5 nodes and the config files,
> would you like to take a look?
> http://apache-ignite-users.70518.x6.nabble.com/Failed-to-
> wait-for-initial-partition-map-exchange-tt6252.html
>
> Thanks,
> -Jason
>
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Fail-to-join-topology-and-repeat-join-
> process-tp6987p7148.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
--
Vladislav Pyatkov
