You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by woo charles <ig...@gmail.com> on 2017/03/29 01:16:17 UTC
Server Client Connection
Hi
I have created 5 server nodes in 5 jvm process in 3 jvms.
After the client node has started up, the oldest server node will establish
a connection to the client node through client's communication port (471XX)
periodically.
May I know the reasons for this?
if it is because of Leader Election, can I have multiple leaders within a
cluster? If yes, how to do it?
Also, can I change this connection behavior (e.g. client connects to
server's communication port)?
Re: Server Client Connection
Posted by Nikolai Tikhonov <nt...@apache.org>.
If you have many open connections on oldest server node it doesn't mean
that whole load will be on it. Ignite distributes data evenly on all server
nodes. Client send request to node which owning requeried data directly.
See details there [1]
1. https://apacheignite.readme.io/docs/data-grid
On Fri, Apr 7, 2017 at 10:54 AM, woo charles <ig...@gmail.com>
wrote:
> Can I move some connections to other nodes in order to reduce the workload
> on the oldest server node?
>
> 2017-04-03 22:26 GMT+08:00 Nikolai Tikhonov <nt...@apache.org>:
>
>> Yes, it's absolutely ok. Do not worry:)
>>
>> On Mon, Apr 3, 2017 at 5:01 AM, woo charles <ig...@gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>>
>>> >I have created 5 server nodes in 5 jvm process in 3 jvms.
>>> To be honest this point is not clear for me. Could you please describe
>>> how you run 5 jvm process in 3 jvms?
>>> Sorry for confused you. It should be "create 5 server nodes(java) in 3
>>> server".
>>>
>>> > After the client node has started up, the oldest server node will
>>> establish a connection to the client node through client's
>>> communication port (471XX) periodically.
>>> It's expected behavior one server node of cluster have direct connection
>>> with client node. Ignite cluster requires that each nodes have direct
>>> connection to any nodes of grid. You can change port range in
>>> TcpCommunicationSpi [1] and TcpDiscoverySpi [2].
>>> But I found that the oldest server node will establish connection to *all
>>> *client nodes. Is it normal?
>>>
>>>
>>>
>>> 2017-03-29 21:49 GMT+08:00 Nikolai Tikhonov <nt...@apache.org>:
>>>
>>>> Hi!
>>>>
>>>> >I have created 5 server nodes in 5 jvm process in 3 jvms.
>>>> To be honest this point is not clear for me. Could you please describe
>>>> how you run 5 jvm process in 3 jvms?
>>>>
>>>> > After the client node has started up, the oldest server node will
>>>> establish a connection to the client node through client's
>>>> communication port (471XX) periodically.
>>>> It's expected behavior one server node of cluster have direct
>>>> connection with client node. Ignite cluster requires that each nodes have
>>>> direct connection to any nodes of grid. You can change port range in
>>>> TcpCommunicationSpi [1] and TcpDiscoverySpi [2].
>>>>
>>>> > if it is because of Leader Election, can I have multiple leaders
>>>> within a cluster? If yes, how to do it?
>>>> You can get more details there [3].
>>>>
>>>> 1. https://apacheignite.readme.io/docs/clustering
>>>> 2. https://apacheignite.readme.io/docs/network-config
>>>> 3. https://apacheignite.readme.io/docs/leader-election
>>>>
>>>>
>>>> On Wed, Mar 29, 2017 at 4:16 AM, woo charles <ignite.charlesw@gmail.com
>>>> > wrote:
>>>>
>>>>> Hi
>>>>>
>>>>> I have created 5 server nodes in 5 jvm process in 3 jvms.
>>>>>
>>>>> After the client node has started up, the oldest server node will
>>>>> establish a connection to the client node through client's communication
>>>>> port (471XX) periodically.
>>>>>
>>>>> May I know the reasons for this?
>>>>> if it is because of Leader Election, can I have multiple leaders
>>>>> within a cluster? If yes, how to do it?
>>>>> Also, can I change this connection behavior (e.g. client connects to
>>>>> server's communication port)?
>>>>>
>>>>
>>>>
>>>
>>
>
Re: Server Client Connection
Posted by woo charles <ig...@gmail.com>.
Can I move some connections to other nodes in order to reduce the workload
on the oldest server node?
2017-04-03 22:26 GMT+08:00 Nikolai Tikhonov <nt...@apache.org>:
> Yes, it's absolutely ok. Do not worry:)
>
> On Mon, Apr 3, 2017 at 5:01 AM, woo charles <ig...@gmail.com>
> wrote:
>
>> Hi,
>>
>>
>> >I have created 5 server nodes in 5 jvm process in 3 jvms.
>> To be honest this point is not clear for me. Could you please describe
>> how you run 5 jvm process in 3 jvms?
>> Sorry for confused you. It should be "create 5 server nodes(java) in 3
>> server".
>>
>> > After the client node has started up, the oldest server node will
>> establish a connection to the client node through client's communication
>> port (471XX) periodically.
>> It's expected behavior one server node of cluster have direct connection
>> with client node. Ignite cluster requires that each nodes have direct
>> connection to any nodes of grid. You can change port range in
>> TcpCommunicationSpi [1] and TcpDiscoverySpi [2].
>> But I found that the oldest server node will establish connection to *all
>> *client nodes. Is it normal?
>>
>>
>>
>> 2017-03-29 21:49 GMT+08:00 Nikolai Tikhonov <nt...@apache.org>:
>>
>>> Hi!
>>>
>>> >I have created 5 server nodes in 5 jvm process in 3 jvms.
>>> To be honest this point is not clear for me. Could you please describe
>>> how you run 5 jvm process in 3 jvms?
>>>
>>> > After the client node has started up, the oldest server node will
>>> establish a connection to the client node through client's
>>> communication port (471XX) periodically.
>>> It's expected behavior one server node of cluster have direct connection
>>> with client node. Ignite cluster requires that each nodes have direct
>>> connection to any nodes of grid. You can change port range in
>>> TcpCommunicationSpi [1] and TcpDiscoverySpi [2].
>>>
>>> > if it is because of Leader Election, can I have multiple leaders
>>> within a cluster? If yes, how to do it?
>>> You can get more details there [3].
>>>
>>> 1. https://apacheignite.readme.io/docs/clustering
>>> 2. https://apacheignite.readme.io/docs/network-config
>>> 3. https://apacheignite.readme.io/docs/leader-election
>>>
>>>
>>> On Wed, Mar 29, 2017 at 4:16 AM, woo charles <ig...@gmail.com>
>>> wrote:
>>>
>>>> Hi
>>>>
>>>> I have created 5 server nodes in 5 jvm process in 3 jvms.
>>>>
>>>> After the client node has started up, the oldest server node will
>>>> establish a connection to the client node through client's communication
>>>> port (471XX) periodically.
>>>>
>>>> May I know the reasons for this?
>>>> if it is because of Leader Election, can I have multiple leaders within
>>>> a cluster? If yes, how to do it?
>>>> Also, can I change this connection behavior (e.g. client connects to
>>>> server's communication port)?
>>>>
>>>
>>>
>>
>
Re: Server Client Connection
Posted by Nikolai Tikhonov <nt...@apache.org>.
Yes, it's absolutely ok. Do not worry:)
On Mon, Apr 3, 2017 at 5:01 AM, woo charles <ig...@gmail.com>
wrote:
> Hi,
>
>
> >I have created 5 server nodes in 5 jvm process in 3 jvms.
> To be honest this point is not clear for me. Could you please describe how
> you run 5 jvm process in 3 jvms?
> Sorry for confused you. It should be "create 5 server nodes(java) in 3
> server".
>
> > After the client node has started up, the oldest server node will
> establish a connection to the client node through client's communication
> port (471XX) periodically.
> It's expected behavior one server node of cluster have direct connection
> with client node. Ignite cluster requires that each nodes have direct
> connection to any nodes of grid. You can change port range in
> TcpCommunicationSpi [1] and TcpDiscoverySpi [2].
> But I found that the oldest server node will establish connection to *all
> *client nodes. Is it normal?
>
>
>
> 2017-03-29 21:49 GMT+08:00 Nikolai Tikhonov <nt...@apache.org>:
>
>> Hi!
>>
>> >I have created 5 server nodes in 5 jvm process in 3 jvms.
>> To be honest this point is not clear for me. Could you please describe
>> how you run 5 jvm process in 3 jvms?
>>
>> > After the client node has started up, the oldest server node will
>> establish a connection to the client node through client's communication
>> port (471XX) periodically.
>> It's expected behavior one server node of cluster have direct connection
>> with client node. Ignite cluster requires that each nodes have direct
>> connection to any nodes of grid. You can change port range in
>> TcpCommunicationSpi [1] and TcpDiscoverySpi [2].
>>
>> > if it is because of Leader Election, can I have multiple leaders within
>> a cluster? If yes, how to do it?
>> You can get more details there [3].
>>
>> 1. https://apacheignite.readme.io/docs/clustering
>> 2. https://apacheignite.readme.io/docs/network-config
>> 3. https://apacheignite.readme.io/docs/leader-election
>>
>>
>> On Wed, Mar 29, 2017 at 4:16 AM, woo charles <ig...@gmail.com>
>> wrote:
>>
>>> Hi
>>>
>>> I have created 5 server nodes in 5 jvm process in 3 jvms.
>>>
>>> After the client node has started up, the oldest server node will
>>> establish a connection to the client node through client's communication
>>> port (471XX) periodically.
>>>
>>> May I know the reasons for this?
>>> if it is because of Leader Election, can I have multiple leaders within
>>> a cluster? If yes, how to do it?
>>> Also, can I change this connection behavior (e.g. client connects to
>>> server's communication port)?
>>>
>>
>>
>
Re: Server Client Connection
Posted by woo charles <ig...@gmail.com>.
Hi,
>I have created 5 server nodes in 5 jvm process in 3 jvms.
To be honest this point is not clear for me. Could you please describe how
you run 5 jvm process in 3 jvms?
Sorry for confused you. It should be "create 5 server nodes(java) in 3
server".
> After the client node has started up, the oldest server node will
establish a connection to the client node through client's communication
port (471XX) periodically.
It's expected behavior one server node of cluster have direct connection
with client node. Ignite cluster requires that each nodes have direct
connection to any nodes of grid. You can change port range in
TcpCommunicationSpi [1] and TcpDiscoverySpi [2].
But I found that the oldest server node will establish connection to
*all *client
nodes. Is it normal?
2017-03-29 21:49 GMT+08:00 Nikolai Tikhonov <nt...@apache.org>:
> Hi!
>
> >I have created 5 server nodes in 5 jvm process in 3 jvms.
> To be honest this point is not clear for me. Could you please describe how
> you run 5 jvm process in 3 jvms?
>
> > After the client node has started up, the oldest server node will
> establish a connection to the client node through client's communication
> port (471XX) periodically.
> It's expected behavior one server node of cluster have direct connection
> with client node. Ignite cluster requires that each nodes have direct
> connection to any nodes of grid. You can change port range in
> TcpCommunicationSpi [1] and TcpDiscoverySpi [2].
>
> > if it is because of Leader Election, can I have multiple leaders within
> a cluster? If yes, how to do it?
> You can get more details there [3].
>
> 1. https://apacheignite.readme.io/docs/clustering
> 2. https://apacheignite.readme.io/docs/network-config
> 3. https://apacheignite.readme.io/docs/leader-election
>
>
> On Wed, Mar 29, 2017 at 4:16 AM, woo charles <ig...@gmail.com>
> wrote:
>
>> Hi
>>
>> I have created 5 server nodes in 5 jvm process in 3 jvms.
>>
>> After the client node has started up, the oldest server node will
>> establish a connection to the client node through client's communication
>> port (471XX) periodically.
>>
>> May I know the reasons for this?
>> if it is because of Leader Election, can I have multiple leaders within a
>> cluster? If yes, how to do it?
>> Also, can I change this connection behavior (e.g. client connects to
>> server's communication port)?
>>
>
>
Re: Server Client Connection
Posted by Nikolai Tikhonov <nt...@apache.org>.
Hi!
>I have created 5 server nodes in 5 jvm process in 3 jvms.
To be honest this point is not clear for me. Could you please describe how
you run 5 jvm process in 3 jvms?
> After the client node has started up, the oldest server node will
establish a connection to the client node through client's communication
port (471XX) periodically.
It's expected behavior one server node of cluster have direct connection
with client node. Ignite cluster requires that each nodes have direct
connection to any nodes of grid. You can change port range in
TcpCommunicationSpi [1] and TcpDiscoverySpi [2].
> if it is because of Leader Election, can I have multiple leaders within a
cluster? If yes, how to do it?
You can get more details there [3].
1. https://apacheignite.readme.io/docs/clustering
2. https://apacheignite.readme.io/docs/network-config
3. https://apacheignite.readme.io/docs/leader-election
On Wed, Mar 29, 2017 at 4:16 AM, woo charles <ig...@gmail.com>
wrote:
> Hi
>
> I have created 5 server nodes in 5 jvm process in 3 jvms.
>
> After the client node has started up, the oldest server node will
> establish a connection to the client node through client's communication
> port (471XX) periodically.
>
> May I know the reasons for this?
> if it is because of Leader Election, can I have multiple leaders within a
> cluster? If yes, how to do it?
> Also, can I change this connection behavior (e.g. client connects to
> server's communication port)?
>