Hello!
As a rule, a faulty thick client can destabilize a cluster. Ignite's
architecture assumes that all clients are collocated, i.e. that the network
between any two nodes (including clients) is reliable, fast and low-latency.
It is not recommended to connect thick clients from different networks. Use
thin clients where possible.
You can file a ticket against Apache Ignite JIRA regarding visor behavior
if you like.
Regards,
--
Ilya Kasnacheev
пт, 7 июн. 2019 г. в 23:15, John Smith <java.dev....@gmail.com>:
> Correct. Should it not at least timeout and at least show what it has
> available? Basically we have a central cluster and various clients connect
> to it from different networks. As an example: Docker containers.
>
> We make sure that the clients are client nodes only and we avoid creating
> any caches on clients.
>
> On Fri, 7 Jun 2019 at 10:19, Ilya Kasnacheev <ilya.kasnach...@gmail.com>
> wrote:
>
>> Hello!
>>
>> I think that Visor will talk to all nodes when trying to run caches
>> command, and if it can't reach client nodes the operation will never finish.
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> ср, 5 июн. 2019 г. в 22:34, John Smith <java.dev....@gmail.com>:
>>
>>> Hi, any thoughts on this?
>>>
>>> On Fri, 31 May 2019 at 10:21, John Smith <java.dev....@gmail.com> wrote:
>>>
>>>> I think it should at least time out and show stats of the nodes it
>>>> could reach? I don't see why it's dependant on client nodes.
>>>>
>>>> On Thu, 30 May 2019 at 11:58, John Smith <java.dev....@gmail.com>
>>>> wrote:
>>>>
>>>>> Sorry pressed enter to quickly....
>>>>>
>>>>> So basically I'm 100% sure if visor cache command cannot reach the
>>>>> client node then it just stays there not doing anything.
>>>>>
>>>>> On Thu, 30 May 2019 at 11:57, John Smith <java.dev....@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi, running 2.7.0
>>>>>>
>>>>>> - I have a 4 node cluster and it seems to be running ok.
>>>>>> - I have clients connecting and doing what they need to do.
>>>>>> - The clients are set as client = true.
>>>>>> - The clients are also connecting from various parts of the network.
>>>>>>
>>>>>> The problem with ignite visor cache command is if visor cannot reach
>>>>>> a specific client node it just seems to hang indefinitely.
>>>>>>
>>>>>> Choose node number ('c' to cancel) [0]: c
>>>>>> visor> cache
>>>>>>
>>>>>> It just stays like that no errors printed nothing...
>>>>>>
>>>>>
