Cluster rebalancing when one node dies

[Amit Pandey]

Hi All,

We are facing an issue , due to some misunderstanding may be on our part of
ignite.

We have a 2 node Ignite cluster configured with persistence.  We have a APi
to activate it, when the two nodes are up we hit the api to activate the
cluster and it works.

However then one node went down , we patched the node and restarted it, but
when request goes to that node we get the following error :-
org.apache.ignite.IgniteException:
Can not perform the operation because the cluster is inactive. Note, that
the cluster is considered inactive by default if Ignite Persistent Store is
used to let all the nodes join the cluster. To activate the cluster call
Ignite.active(true).

We had set the baseline Topology to 2 and on checking I saw the current
state is "NODES":1,"BT":2

Can anyone please help on what we should do ?

Re: Re client node connects to server nodes behind NAT

[Denis Magda]

Hi Ma,

Streaming is supported for the thin clients (see a related discussion on
the user list). As for the peer-class-loading support, not sure that it's
coming. As an alternative, you can implement the UriDeploymentSpi interface
that will load/reload code from your custom location/repository:
https://ignite.apache.org/docs/latest/code-deployment/deploying-user-code

If you don't want to bother with the UriDeploymentSpi implementation, then
check this Deployment feature of GridGain Nebula (it will be available for
non-Nebula clusters through the same Control Center interface soon). That
feature implements the UriDeploymentSpi:
https://www.youtube.com/watch?v=8hS1ux1d3Ck&list=PLMc7NR20hA-J5tnwx-ltnBB9X-gF8cP9S&index=2

Finally, as Max suggested, configure the thick client and server nodes
following this documentation:
https://ignite.apache.org/docs/latest/clustering/running-client-nodes-behind-nat
(it should solve your networking problems).

-
Denis


On Tue, Nov 16, 2021 at 2:53 AM Maksim Timonin 
wrote:

> Hi!
>
> Unfortunately, support of peer class loading and data streams is limited
> for thin clients. AFAIK, .Net thin client supports data streamer.
>
> I found that Ignite has a special mode of running client nodes
> `forceClientToServerConnections` [1]. But this feature is marked as
> experimental since 2.9 and I don't see any updates there. Actually, I'm not
> aware about this feature much. I found the feature discussion on dev list
> [2]. Maybe somebody from the community can say more about this feature. But
> looks like it can be a solution in your case.
>
> [1]
> https://ignite.apache.org/docs/latest/clustering/running-client-nodes-behind-nat
> [2] https://www.mail-archive.com/dev@ignite.apache.org/msg44990.html
>
> On Mon, Nov 15, 2021 at 12:15 PM MJ <6733...@qq.com> wrote:
>
>> That would be peer class loading && data stream .
>>
>> Thanks
>>
>> -- 原始邮件 --
>> *发件人:* "user" ;
>> *发送时间:* 2021年11月15日(星期一) 下午3:59
>> *收件人:* "user";
>> *主题:* Re: client node connects to server nodes behind NAT
>>
>> Hi, I'll touch on a similar topic a little tomorrow on IgniteSummit [1],
>> you're welcome :)
>>
>> But, a thick client is part of topology, and it has to be able to connect
>> every node in the cluster directly, then thick clients have to be run
>> within the same kubernetes cluster. Thin clients were designed to eliminate
>> this problem.
>>
>> What features of thick clients do you want to use?
>>
>> [1] https://ignite-summit.org/sessions/293596
>>
>> On Mon, Nov 15, 2021 at 3:50 AM MJ <6733...@qq.com> wrote:
>>
>>> Hi,
>>>
>>> Is that possible for a non-Kubernetes client node connects to server
>>> nodes within Kubernetes ?
>>>
>>> have read below docs seems impossible
>>>
>>> https://ignite.apache.org/docs/latest/installation/kubernetes/azure-deployment#connecting-client-nodes
>>>
>>> Have tried with thin client outside of Kubernetes - that works fine
>>> client node(thick client) - always throw exceptions, most likely the
>>> internal ips bebind NAT cannot be detected from external , is there any
>>> workaround to implement that non-Kubernetes client node connects to server
>>> nodes within Kubernetes ? I'd like to utilise the power features of thick
>>> client. and They can be depoloyed everywhere if there is the way of making
>>> it.
>>>
>>>
>>>
>>> Thanks,
>>> Ma Jun
>>>
>>

Re: protocol of streaming

[Denis Magda]

Nikita, Igor, looping you in...

Do we folks have tickets for this documentation update?

-
Denis


On Tue, Nov 16, 2021 at 6:11 AM Pavel Tupitsyn  wrote:

> Hello Timothy,
>
> Thin client protocol supports streaming [1],
> the documentation just was not updated yet.
>
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-68%3A+Thin+Client+Data+Streamer
>
> On Tue, Nov 16, 2021 at 2:06 PM Timothy Peng  wrote:
>
>> Hello
>>
>> I looked through this documentation,
>>
>> https://ignite.apache.org/docs/latest/binary-client-protocol/binary-client-protocol
>>
>> It seems that the binary client protocol doesn't have streaming
>> supported. Am I missing something?
>>
>> Thanks
>>
>

[ANNOUNCE] Apache Ignite Apache Ignite spring-tx-ext, spring-cache-ext extensions 1.0.0 released

[Nikita Amelchev]

The Apache Ignite Community is pleased to announce the release of
Apache Ignite Spring Cache and Spring Transactions extensions 1.0.0.

The following integrations were migrated to the Apache Ignite
Extensions repository:

- Spring Transactions extension
- Spring Cache extension

Apache Ignite Spring Cache extension: release notes [1], documentation [2].
Apache Ignite Spring Transactions extension: release notes [3],
documentation [4].

The sources package is available here:
https://ignite.apache.org/download.cgi#extensions

Please let us know if you have any problems
https://ignite.apache.org/community/resources.html#ask

[1] https://ignite.apache.org/releases/ext/spring-tx-1.0.0/release_notes.html
[2] 
https://ignite.apache.org/docs/2.11.0/extensions-and-integrations/spring/spring-tx.html
[3] https://ignite.apache.org/releases/ext/spring-cache-1.0.0/release_notes.html
[4] 
https://ignite.apache.org/docs/2.11.0/extensions-and-integrations/spring/spring-caching.html

-- 
Best wishes,
Amelchev Nikita

Re: protocol of streaming

[Pavel Tupitsyn]

Hello Timothy,

Thin client protocol supports streaming [1],
the documentation just was not updated yet.

[1]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-68%3A+Thin+Client+Data+Streamer

On Tue, Nov 16, 2021 at 2:06 PM Timothy Peng  wrote:

> Hello
>
> I looked through this documentation,
>
> https://ignite.apache.org/docs/latest/binary-client-protocol/binary-client-protocol
>
> It seems that the binary client protocol doesn't have streaming supported.
> Am I missing something?
>
> Thanks
>

protocol of streaming

[Timothy Peng]

Hello

I looked through this documentation,
https://ignite.apache.org/docs/latest/binary-client-protocol/binary-client-protocol

It seems that the binary client protocol doesn't have streaming supported.
Am I missing something?

Thanks

Re: Run ignite kubernetes pod on java 11

[Stephen Darlington]

I don’t see an image with Java 11. I think you’d have to build your own.

There are tickets for this: https://issues.apache.org/jira/browse/IGNITE-14031 
and https://issues.apache.org/jira/browse/IGNITE-15209

> On 16 Nov 2021, at 09:55, Surinder Mehra  wrote:
> 
> Hi, 
> I followed below link to deploy ignite pod on kubernetes. It uses apache 
> ignite 2.11 docker image which has java openjdk 8. Is there a way to 
> configure java 11 on this  pod or ignite image with jdk11 ?
> 
> https://ignite.apache.org/docs/latest/installation/kubernetes/amazon-eks-deployment
>  
> 

Run ignite kubernetes pod on java 11

[Surinder Mehra]

Hi,
I followed below link to deploy ignite pod on kubernetes. It uses apache
ignite 2.11 docker image which has java openjdk 8. Is there a way to
configure java 11 on this  pod or ignite image with jdk11 ?

https://ignite.apache.org/docs/latest/installation/kubernetes/amazon-eks-deployment

Re: Ignite on a server

[Timothy Peng]

Thank you Gianluca. Yes we have been using Ignite happily in the
development environment.

On Tue, Nov 16, 2021 at 5:38 PM Gianluca Bonetti 
wrote:

> Hello Timothy
>
> I usually deploy on more servers, but just 2 to 4, I don't have larger
> deployments.
> I also have single server deployments.
> In my opinion and personal experience, native Java integration by Ignite
> with persistent storage is definitely better than a "hybrid" solution (some
> other software plus a Java client) like going to external caches like Redis.
> I've seen benchmarks in the past where Ignite also performed better.
> Don't know the current status as of today, but not my concern at all, as
> using Apache Ignite is definitely too easy and too fast to even consider
> alternatives.
> Some other developers may have had different experiences, just wanted to
> share my point of view.
>
> Cheers
> Gianluca
>
>
> Il giorno mar 16 nov 2021 alle ore 04:33 Timothy Peng 
> ha scritto:
>
>> @Surinder, @Ilya,
>>
>> Can you tell what's the advantages for memory storage compared to other
>> products such as Redis?
>>
>> Thanks.
>>
>>
>> On Tue, Nov 16, 2021 at 11:27 AM Surinder Mehra 
>> wrote:
>>
>>> So it is a very broad question. Sure you can use it for caching and
>>> compute as well as it has enough cores. Depending upon your requirements,
>>> you can read about data grid part on ignite documentation to get details
>>> about various ignite cache configurations
>>> - in memory
>>> - in memory with cache stores (IMDG)
>>> - caches with  native persistence(IMDB)
>>> - on heap or off heap caches
>>>
>>> Just some pointers to read
>>>
>>> On Tue, Nov 16, 2021, 08:34 Timothy Peng  wrote:
>>>
 Hello

 I just have one dedicated server who has 128GB memory and 16 cores.
 Can I deploy Ignite on this server and just use the memory cache
 feature?

 Thanks

>>>

Re: Ignite on a server

[Gianluca Bonetti]

Hello Timothy

I usually deploy on more servers, but just 2 to 4, I don't have larger
deployments.
I also have single server deployments.
In my opinion and personal experience, native Java integration by Ignite
with persistent storage is definitely better than a "hybrid" solution (some
other software plus a Java client) like going to external caches like Redis.
I've seen benchmarks in the past where Ignite also performed better.
Don't know the current status as of today, but not my concern at all, as
using Apache Ignite is definitely too easy and too fast to even consider
alternatives.
Some other developers may have had different experiences, just wanted to
share my point of view.

Cheers
Gianluca


Il giorno mar 16 nov 2021 alle ore 04:33 Timothy Peng 
ha scritto:

> @Surinder, @Ilya,
>
> Can you tell what's the advantages for memory storage compared to other
> products such as Redis?
>
> Thanks.
>
>
> On Tue, Nov 16, 2021 at 11:27 AM Surinder Mehra 
> wrote:
>
>> So it is a very broad question. Sure you can use it for caching and
>> compute as well as it has enough cores. Depending upon your requirements,
>> you can read about data grid part on ignite documentation to get details
>> about various ignite cache configurations
>> - in memory
>> - in memory with cache stores (IMDG)
>> - caches with  native persistence(IMDB)
>> - on heap or off heap caches
>>
>> Just some pointers to read
>>
>> On Tue, Nov 16, 2021, 08:34 Timothy Peng  wrote:
>>
>>> Hello
>>>
>>> I just have one dedicated server who has 128GB memory and 16 cores.
>>> Can I deploy Ignite on this server and just use the memory cache feature?
>>>
>>> Thanks
>>>
>>