You mean the connection config for visor to connect to the cluster?
On Wed., Jul. 8, 2020, 5:53 p.m. Humphrey, wrote:
> Not sure if this will help, I've also had issues with Visor keeps hanging
> the
> cluster.
>
> When I changed the configuration to ClientMode (default is ServerMode) it
>
Not sure if this will help, I've also had issues with Visor keeps hanging the
cluster.
When I changed the configuration to ClientMode (default is ServerMode) it
solved my problem. Might be good to give it a try.
Humphrey
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Thanks, John. That connectivity improvement fixes situations when a server
needs to open a connection to a client but fails. The client will be
opening the connection instead after getting a special message via the
discovery networking layer. It won’t improve the communication between
Visor and
Sorry, mixed the thread, it the one that asks if server nodes connect back
to thick clients and it was you who mentioned the new feature...
On Wed., Jul. 1, 2020, 4:03 p.m. John Smith, wrote:
> If you look for the "what does all partition owners have left mean?"
> thread.
>
> There is mention
If you look for the "what does all partition owners have left mean?" thread.
There is mention to improve the protocol so that other nodes don't need to
connect to clients running inside containers... It links to another thread
indicating that there may be a PR to add a flag of some sort to mark
>
> But you guys also mentioned in my other thread that you are working on a
> feature that doesn't require connecting to the client when it's running
> inside a container.
What is the tread you're referring to? Visor always will be connecting to
the clients regardless of your deployment
Hi, yes I figured that visor is just another thick client.
By using address resolver on my thick client applications inside container
everything works fine and visor also connects properly (no need to add all
client configs everywhere).
As stated it just adds tiny delay when visor needs to
Hi John,
As Stephen mentioned, Visor connects to the cluster in a way similar to
server nodes and thick clients. It's connected as a daemon node that is
filtered out from metrics and other public APIs. That's why you don't see
Visor being reported in the cluster topology metrics along with
It’s not that Visor connects to a thick client, it’s that it is a thick client.
There are some weird implementation details — like it’s written in Scala and
using “daemon mode” — but it becomes part of the cluster, so the same “rules”
apply as any other thick client. Connections to other nodes
So this is what I gathered from this experience.
When running commands on Visor's console, Visor will attempt to connect to
the thick client.
For example if you type the "node" command and attempt to get detailed
statistics for a specific thick client, Visor will pause on the data region
stats
Ok so. Is this expected behaviour? From user perspective this seems like a
bug.
Visor is supposed to be used as a way to monitor...
So if as a user we enter a command and it just freezes indefinently it just
seems unfriendly.
In another thread the the team mentioned that they are working on
Hello!
I can see the following in the thread dump:
"main" #1 prio=5 os_prio=0 tid=0x7f02c400d800 nid=0x1e43 runnable
[0x7f02cad1e000]
java.lang.Thread.State: RUNNABLE
at sun.nio.ch.Net.poll(Native Method)
at sun.nio.ch.SocketChannelImpl.poll(SocketChannelImpl.java:951)
- locked
Ok.
I am able to reproduce the "issue" unless we have a misunderstanding and we
are talking about the same thing...
My thick client runs inside a container in a closed network NOT bridged and
NOT host. I added a flag to my application that allows it to add the
address resolver to the config.
1-
Hello!
The easiest way is jstack
Regards,
--
Ilya Kasnacheev
пн, 29 июн. 2020 г. в 20:20, John Smith :
> How?
>
> On Mon, 29 Jun 2020 at 12:03, Ilya Kasnacheev
> wrote:
>
>> Hello!
>>
>> Try collecting thread dump from Visor as it freezes.
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>>
How?
On Mon, 29 Jun 2020 at 12:03, Ilya Kasnacheev
wrote:
> Hello!
>
> Try collecting thread dump from Visor as it freezes.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пн, 29 июн. 2020 г. в 18:11, John Smith :
>
>> How though?
>>
>> 1- Entered node command
>> 2- Got list of nodes, including thick
Hello!
Try collecting thread dump from Visor as it freezes.
Regards,
--
Ilya Kasnacheev
пн, 29 июн. 2020 г. в 18:11, John Smith :
> How though?
>
> 1- Entered node command
> 2- Got list of nodes, including thick clients
> 3- Selected thick client
> 4- Entered Y for detailed statistics
> 5-
How though?
1- Entered node command
2- Got list of nodes, including thick clients
3- Selected thick client
4- Entered Y for detailed statistics
5- Snapshot details displayed
6- Data region stats frozen
I think the address resolution is working for this as well. I need to
confirm. Because I fixed
Hello!
This usually means there's no connectivity between node and Visor.
Regards,
--
Ilya Kasnacheev
пн, 29 июн. 2020 г. в 17:01, John Smith :
> Also I think for Visor as well?
>
> When I do top or node commands, I can see the thick client. But when I
> look at detailed statistics for that
Also I think for Visor as well?
When I do top or node commands, I can see the thick client. But when I look
at detailed statistics for that particular thick client it freezes
"indefinitely". Regular statistics it seems ok.
On Mon, 29 Jun 2020 at 08:08, Ilya Kasnacheev
wrote:
> Hello!
>
> For
Hello!
For thick clients, you need both 47100 and 47500, both directions (perhaps
for 47500 only client -> server is sufficient, but for 47100, both are
needed).
For thin clients, 10800 is enough. For control.sh, 11211.
Regards,
--
Ilya Kasnacheev
пт, 26 июн. 2020 г. в 22:06, John Smith :
>
I'm askin in separate question so people can search for it if they ever
come across this...
My server nodes are started as and I also connect the client as such.
foo:47500
...
21 matches
Mail list logo
