Re: Re: ignite client can not reconnect to ignite Kubernetes cluster,after pod restart

ermission? >>> below is my account >>> -- >>> wkhapy...@gmail.com >>> >>> >>> *From:* wkhapy...@gmail.com >>> *Date:* 2022-06-23 22:34 >>> *To:* Pavel Tupitsyn >>> *Subject:* Re: ignite client can not

Re: Re: ignite client can not reconnect to ignite Kubernetes cluster,after pod restart

34 >> *To:* Pavel Tupitsyn >> *Subject:* Re: ignite client can not reconnect to ignite Kubernetes >> cluster,after pod restart >> thank you!i will follow wiki. >> ---Original--- >> *From:* "Pavel Tupitsyn" >> *Date:* Thu, Jun 23, 2022 22:25 PM

Re: ignite client can not reconnect to ignite Kubernetes cluster,after pod restart

ubject:* Re: ignite client can not reconnect to ignite Kubernetes > cluster,after pod restart > > I am interested in ignite > > ---Original--- > *From:* "wkhapy...@gmail.com" > *Date:* Thu, Jun 23, 2022 21:37 PM > *To:* "Pavel Tupitsyn"; > *Subject:* Re:

Re: Re: ignite client can not reconnect to ignite Kubernetes cluster,after pod restart

Hi, ok,I'll try it later. wkhapy...@gmail.com From: Maksim Timonin Date: 2022-06-23 13:53 To: user Subject: Re: ignite client can not reconnect to ignite Kubernetes cluster,after pod restart Hi, Please, try to use `ClientConfiguration#setRetryLimit` additionally to `ClientRetryAllPolicy

Re: ignite client can not reconnect to ignite Kubernetes cluster,after pod restart

Hi, Please, try to use `ClientConfiguration#setRetryLimit` additionally to `ClientRetryAllPolicy`. It should help you. Please let me know if it solves the issue or not. Thanks! On Wed, Jun 22, 2022 at 8:02 AM Ilya Korol wrote: > Hi, > > Please take look to >

RE: ignite client can not reconnect to ignite Kubernetes cluster,after pod restart

Hi, Please take look to https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/client/ClientAddressFinder.html, according to this ThinClientKubernetesAddressFinder should refresh address list on client connection failure, or you can try to set *paritionAwareness = true* in

Re: ignite client can not reconnect to ignite Kubernetes cluster,after pod restart

reason i found ，ignite server node restart ip changed，but ignite client still use old ip address，is there any way refresh address wkhapy...@gmail.com From: f cad Date: 2022-06-22 09:53 To: user Subject: ignite client can not reconnect to ignite Kubernetes cluster,after pod restart below

ignite client can not reconnect to ignite Kubernetes cluster,after pod restart

below if client code config KubernetesConnectionConfiguration kcfg = new KubernetesConnectionConfiguration(); kcfg.setNamespace(igniteK8sNameSpace);kcfg.setServiceName(igniteK8sServiceName);cfg.setAddressesFinder(new ThinClientKubernetesAddressFinder(kcfg));cfg.setRetryPolicy(new

Re: Run ignite kubernetes pod on java 11

;node-configuration.xml" ARG IGNITE_VERSION="2.11.0" #ARG OPTION_LIBS="ignite-kubernetes,ignite-rest-http" ENV IGNITE_HOME /opt/ignite/apache-ignite #ENV CONFIG_URI config/$IGNITE_CFG_XML # Disabling quiet mode. ENV IGNITE_QUIET=false WORKDIR /opt/ignite # Add missi

Re: Run ignite kubernetes pod on java 11

openjdk drwxr-xr-x5 root root39 May 11 2019 java-1.8-openjdk drwxr-xr-x 10 root root 185 Nov 18 09:01 java-11-openjdk bash-4.4# Regards, On Thu, Nov 18, 2021 at 2:00 PM Maksim Timonin wrote: > Hi, you should move ignite-kubernetes (and others optional libs y

Re: Run ignite kubernetes pod on java 11

Hi, you should move ignite-kubernetes (and others optional libs you're going to use) from optional to $IGNITE_HOME/libs/ On Wed, Nov 17, 2021 at 6:50 PM Surinder Mehra wrote: > Thanks for the suggestion. I tried to fix dependencies and it works with > default-ignite-config.xml, which mean

Re: Run ignite kubernetes pod on java 11

ame. >> ARG IGNITE_CFG_XML="node-configuration.xml" >> >> # Set Apache Ignite version. >> ARG IGNITE_VERSION="2.11.0" >> >> # Set IGNITE_HOME variable. >> ENV IGNITE_HOME /opt/ignite/apache-ignite-${IGNITE_VERSION}-bin >> >> # Set

Re: Run ignite kubernetes pod on java 11

e-${IGNITE_VERSION}-bin > > # Set a path to the Apache Ignite configuration file. Use the run.sh script > below: > ENV CONFIG_URI ${IGNITE_HOME}/config/$IGNITE_CFG_XML > > # Make sure the Kubernetes lib is copied to the 'libs' folder. > #ENV OPTION_LIBS ignite-kubernetes >

Re: Run ignite kubernetes pod on java 11

G IGNITE_VERSION="2.11.0" > > # Set IGNITE_HOME variable. > ENV IGNITE_HOME /opt/ignite/apache-ignite-${IGNITE_VERSION}-bin > > # Set a path to the Apache Ignite configuration file. Use the run.sh script > below: > ENV CONFIG_URI ${IGNITE_HOME}/config/$IGNITE_C

Re: Run ignite kubernetes pod on java 11

}-bin # Set a path to the Apache Ignite configuration file. Use the run.sh script below: ENV CONFIG_URI ${IGNITE_HOME}/config/$IGNITE_CFG_XML # Make sure the Kubernetes lib is copied to the 'libs' folder. #ENV OPTION_LIBS ignite-kubernetes # Disabling quiet mode. ENV IGNITE_QUIET=false WORKDIR /opt/ign

Re: Run ignite kubernetes pod on java 11

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

Run ignite kubernetes pod on java 11

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: Apache Ignite Kubernetes Stateful deployment with parallel pod management

Thanks Alex for the response. Parallel pod management is working. Earlier I added readiness and liveness probes, with initial delay of 180 seconds for the Ignite pods in stateful set because of which no traffic was allowed to pods, and hence the discovery failed. After removing these probes,

Re: Apache Ignite Kubernetes Stateful deployment with parallel pod management

Hi, I am not getting the same result in my setup. Parallel pod management works correctly. Send over your YAML configs (including service ignite config, and stateful set descriptors). Make sure you followed the example here:

Apache Ignite Kubernetes Stateful deployment with parallel pod management

Hi, I am trying to deploy Apache Ignite using a Statefulset with four Ignite pods in Kubernetes. I have my Ignite service deployed already and ip finder set properly in ignite configuration. 1. When I set pod management policy to "OrderedReady" in statefulset - which means each Ignite pod

Re: ignite-kubernetes seems to be missing the jackson-annotations dependency

5, kellan wrote: > > While trying to run ignite 2.7 with the ignite-kubernetes package I'm getting > this error at start-up: > > java.lang.NoClassDefFoundError: com/fasterxml/jackson/annotation/JsonView > at > com.fasterxml.jackson.databind.introspect

ignite-kubernetes seems to be missing the jackson-annotations dependency

While trying to run ignite 2.7 with the ignite-kubernetes package I'm getting this error at start-up: java.lang.NoClassDefFoundError: com/fasterxml/jackson/annotation/JsonView at com.fasterxml.jackson.databind.introspect.JacksonAnnotationIntrospector.(JacksonAnnotationIntrospector.java:37

Re: Los Angeles Area Apache Ignite/Kubernetes Meetup

cross-posting to the user list > On Jan 10, 2018, at 3:17 PM, Dani Traphagen wrote: > > Hi everyone, > > > *January 31st *I will be speaking in Los Angeles at *Verizon Digital Media > Services* on using Apache Ignite with Kubernetes! > > > You can read all the meetup

Los Angeles Area Apache Ignite/Kubernetes Meetup

Hi everyone, *January 31st *I will be speaking in Los Angeles at *Verizon Digital Media Services* on using Apache Ignite with Kubernetes! You can read all the meetup details here along with the abstract description. Free

Re: New Blogs: What's new in Ignite.NET 1.9 and Ignite Kubernetes deployment on Azure

ng Ignite in Kubernetes in Microsof Azure by me: > https://www.gridgain.com/resources/blog/deploying-apache-ignite-kubernetes-microsoft-azure > > <https://www.gridgain.com/resources/blog/deploying-apache-ignite-kubernetes-microsoft-azure> > > Soon the post will

New Blogs: What's new in Ignite.NET 1.9 and Ignite Kubernetes deployment on Azure

/resources/blog/deploying-apache-ignite-kubernetes-microsoft-azure Soon the post will be added to Ignite’s blog feed: https://ignite.apache.org/blogs.html <https://ignite.apache.org/blogs.html> If you blog about Ignite please let me know and we will promote your job over the feed, t

Re: Ignite & Kubernetes

overy> > > Also, it is likely that it will work smoothly with Ignite docker container: > https://ignite.apache.org/download.cgi#docker > <https://ignite.apache.org/download.cgi#docker> > > D. > > On Thu, Apr 28, 2016 at 6:50 AM, Christos Erotocritou <chris...@gridg

Re: Ignite & Kubernetes

> https://ignite.apache.org/download.cgi#docker >>> >>> D. >>> >>> On Thu, Apr 28, 2016 at 6:50 AM, Christos Erotocritou < >>> chris...@gridgain.com> wrote: >>> >>>> Hi all, >>>> >>>> Is anyone working with Ignite & kubernetes? >>>> >>>> Moreover I’d like to understand how it would be possible to do auto >>>> discovery of new Ignite nodes. >>>> >>>> Thanks, >>>> >>>> Christos >>> >>> >>> >

Re: Ignite & Kubernetes

ker >> container: >> https://ignite.apache.org/download.cgi#docker >> >> D. >> >> On Thu, Apr 28, 2016 at 6:50 AM, Christos Erotocritou < >> chris...@gridgain.com> wrote: >> >>> Hi all, >>> >>> Is anyone working with Ignite & kubernetes? >>> >>> Moreover I’d like to understand how it would be possible to do auto >>> discovery of new Ignite nodes. >>> >>> Thanks, >>> >>> Christos >> >> >>

Re: Ignite & Kubernetes

based-discovery > > Also, it is likely that it will work smoothly with Ignite docker container: > https://ignite.apache.org/download.cgi#docker > > D. > > On Thu, Apr 28, 2016 at 6:50 AM, Christos Erotocritou < > chris...@gridgain.com> wrote: > >> Hi all, >> &

Ignite & Kubernetes

Hi all, Is anyone working with Ignite & kubernetes? Moreover I’d like to understand how it would be possible to do auto discovery of new Ignite nodes. Thanks, Christos