ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexey Kuznetsov <akuznet...@apache.org>
Subject Re: [GridCachePartitionExchangeManager] Pending transaction deadlock detection futures
Date Wed, 29 Mar 2017 10:20:10 GMT
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 <
valentin.kulichenko@gmail.com> wrote:

> cross-posting to dev list.
>
> Guys,
>
> Does anyone have an idea why client mode in Visor affects behavior? I
> thought we already forced client mode there, no?
>
> Alexey, you should know the answer. Can you please take a look at this
> thread?
>
> -Val
>
>
> On Tue, Mar 28, 2017 at 7:02 AM, ght230 <ght230@163.com> wrote:
>
>> Yes,I use custom build.
>>
>> Today I tried to set Ignition.setClientMode(true) for command "open" of
>> the
>> visorcmd.
>>
>> It seems the visorcmd will not stuck the whole cluster again.
>>
>> Is there anything wrong in "ClientMode" of the visorcmd?
>>
>>
>>
>> --
>> View this message in context: http://apache-ignite-users.705
>> 18.x6.nabble.com/GridCachePartitionExchangeManager-Pending-t
>> ransaction-deadlock-detection-futures-tp11362p11501.html
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>
>
>


-- 
Alexey Kuznetsov

Mime
View raw message