Re: Thin Client connection not working...

[Ilya Kasnacheev]

Hello!

I'm pretty sure I had an in-memory node active at the same time.

Regards,
-- 
Ilya Kasnacheev


ср, 25 нояб. 2020 г. в 09:05, Wolfgang Meyerle <
wolfgang.meye...@googlemail.com>:

> Seems like you're missing starting up youre ignite server node.
>
> try this:
>
> ./ignite.sh
>
> after the node has started activate the node with
>
> ./control.sh --activate
>
>
> I ran into the same issue...
>
>
> Regards,
>
> Wolfgang
>
> Am 24.11.20 um 4:41 PM schrieb Ilya Kasnacheev:
> >
> >  >
> 
> >  > *Von:* Stephen Darlington  > >
>

Re: Add node automatically to Ignite

[Stephen Darlington]

Yes.

> On 25 Nov 2020, at 12:31, Amit Pandey  wrote:
> 
> I want to do a check then so,
> 
> if I do , the below when cluster is activated then if I add or remove nodes 
> after a given time Ignite will take care of the balancing ? Is that 
> understanding correct? In our case its not possible to use the control script
> ignite.cluster().baselineAutoAdjustEnabled(true);
> 
> ignite.cluster().baselineAutoAdjustTimeout(3);
> 
> On Wed, Nov 25, 2020 at 3:04 PM Stephen Darlington 
> mailto:stephen.darling...@gridgain.com>> 
> wrote:
> Once you’ve activated your cluster, you need to add and remove nodes from the 
> baseline manually. The most common method is "control.sh —baseline 
> add/remove" but there’s also an API.
> 
> You could also consider baseline topology auto-adjustment, but you need to be 
> very careful that you don’t move data around unnecessarily.
> 
> Both are documented here:
> 
> https://ignite.apache.org/docs/latest/clustering/baseline-topology#baseline-topology-in-persistent-clusters
>  
> 
> 
> Regards,
> Stephen
> 
>> On 24 Nov 2020, at 20:01, Amit Pandey > > wrote:
>> 
>> Just to add that the issue is that all our caches are replicated and it 
>> seems that when we hit the new node we dont get data replicated at all.
>> 
>> Regards
>> 
>> On Wed, Nov 25, 2020 at 1:29 AM Amit Pandey > > wrote:
>> Hi,
>> 
>> I have a cluster of Ignite nodes running with persistence with docker. So we 
>> activate the cluster programmatically the first time and it works fine.
>> 
>> However , when a node fails and we have to add a new node in its place we 
>> are seeing that its not joining the cluster.
>> 
>> is there anyway to fix this ?
>> 
>> regards
> 
> 

Re: Add node automatically to Ignite

[Amit Pandey]

I want to do a check then so,

if I do , the below when cluster is activated then if I add or remove nodes
after a given time Ignite will take care of the balancing ? Is that
understanding correct? In our case its not possible to use the control
script

ignite.cluster().baselineAutoAdjustEnabled(true);
ignite.cluster().baselineAutoAdjustTimeout(3);


On Wed, Nov 25, 2020 at 3:04 PM Stephen Darlington <
stephen.darling...@gridgain.com> wrote:

> Once you’ve activated your cluster, you need to add and remove nodes from
> the baseline manually. The most common method is "control.sh —baseline
> add/remove" but there’s also an API.
>
> You could also consider baseline topology auto-adjustment, but you need to
> be very careful that you don’t move data around unnecessarily.
>
> Both are documented here:
>
>
> https://ignite.apache.org/docs/latest/clustering/baseline-topology#baseline-topology-in-persistent-clusters
>
> Regards,
> Stephen
>
> On 24 Nov 2020, at 20:01, Amit Pandey  wrote:
>
> Just to add that the issue is that all our caches are replicated and it
> seems that when we hit the new node we dont get data replicated at all.
>
> Regards
>
> On Wed, Nov 25, 2020 at 1:29 AM Amit Pandey 
> wrote:
>
>> Hi,
>>
>> I have a cluster of Ignite nodes running with persistence with docker. So
>> we activate the cluster programmatically the first time and it works fine.
>>
>> However , when a node fails and we have to add a new node in its place we
>> are seeing that its not joining the cluster.
>>
>> is there anyway to fix this ?
>>
>> regards
>>
>
>
>

Re: Add node automatically to Ignite

[Stephen Darlington]

Once you’ve activated your cluster, you need to add and remove nodes from the 
baseline manually. The most common method is "control.sh —baseline add/remove" 
but there’s also an API.

You could also consider baseline topology auto-adjustment, but you need to be 
very careful that you don’t move data around unnecessarily.

Both are documented here:

https://ignite.apache.org/docs/latest/clustering/baseline-topology#baseline-topology-in-persistent-clusters

Regards,
Stephen

> On 24 Nov 2020, at 20:01, Amit Pandey  wrote:
> 
> Just to add that the issue is that all our caches are replicated and it seems 
> that when we hit the new node we dont get data replicated at all.
> 
> Regards
> 
> On Wed, Nov 25, 2020 at 1:29 AM Amit Pandey  > wrote:
> Hi,
> 
> I have a cluster of Ignite nodes running with persistence with docker. So we 
> activate the cluster programmatically the first time and it works fine.
> 
> However , when a node fails and we have to add a new node in its place we are 
> seeing that its not joining the cluster.
> 
> is there anyway to fix this ?
> 
> regards

Re: Apache Ignite Clientside NearCache and Serverside Eviction blocking cluster

[Вячеслав Коптилин]

Hello Prasad,

I will take a look and file a ticket if needed.

Thanks,
S.

пн, 23 нояб. 2020 г. в 19:23, pvprsd :

> Hi,
>
> Did anyone get a chance to look into this issue? Is this supported
> configuration for ignite? As these 2 (clientside NearCache and serverside
> eviction) are very common features, I am wondering many projects should be
> using this combination.
>
> Can this be reported as a defect for ignite, if there is no configuration
> fix for this problem?
>
> Many thanks in advance.
>
> Thanks,
> Prasad
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>