I have created a JIRA for that.
https://issues.apache.org/jira/browse/IGNITE-4924.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/GridCachePartitionExchangeManager-Pending-transaction-deadlock-detection-futures-tp11362p11767.html
Sent from the Apache Ignite
;
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/GridCachePartitionExchangeManager-Pending-transaction-
> deadlock-detection-futures-tp11362p11638.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
--
Alexey Kuznetsov
I want to know should Visor CMD be worked in client mode or daemon mode?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/GridCachePartitionExchangeManager-Pending-transaction-deadlock-detection-futures-tp11362p11638.html
Sent from the Apache Ignite Users mailing
Val,
>> Does anyone have an idea why client mode in Visor affects behavior? I
thought we already forced client mode there, no?
Visor CMD was NOT reworked to client mode.
So Visor CMD starts server node in daemon mode.
On Wed, Mar 29, 2017 at 2:28 AM, Valentin Kulichenko <
d?
>
>
>
> --
> View this message in context: http://apache-ignite-users.705
> 18.x6.nabble.com/GridCachePartitionExchangeManager-Pending-
> transaction-deadlock-detection-futures-tp11362p11501.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
/apache-ignite-users.70518.x6.nabble.com/GridCachePartitionExchangeManager-Pending-transaction-deadlock-detection-futures-tp11362p11501.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
dumps required, because they help to find out
the reason of the hang. Please, attach them as well.
-Dmitry.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/GridCachePartitionExchangeManager-Pending-transaction-deadlock-detection-futures-tp11362p11485.html
Sent
Hi,
What operations in visorcmd you did?
Please attach thread dumps (when cluster hangs) and logs from all nodes.
Thanks!
-Dmitry.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/GridCachePartitionExchangeManager-Pending-transaction-deadlock-detection-futures
][exchange-worker-#300%null%][GridCachePartitionExchangeManager] Pending
transaction deadlock detection futures:
[16:52:23,655][WARN ][exchange-worker-#300%null%][TcpCommunicationSpi]
Communication SPI recovery descriptors:
[key=ConnectionKey [nodeId=b0b8409c-36de-42c2-92c2-65f583941e07, idx
