Hello Stephen,
I did try changes you suggested above and I did get output. Thanks for that.
But I am facing a different issue in meantime on my microservice which have
following setup :
- I have set up a kubernetes pod cluster where I have started *3 ignite
nodes and deployed k8s pods
Hi,
*After some days, I was unable to see the created cache on the Ignite
> shell *which I have created and was able to see at first when node
> started properly.
What is Ignite shell? Sqlline?
Now I am getting a *table not found exception* from API request for
> fetching using ignite sql
Hello,
*What is Ignite shell? Sqlline? - > *Yes sqlline.
*It looks like all cluster nodes have failed or restarted. - >* May be
because K8s pods are getting restarted as per container restart policy.
*Is this maybe the case? This policy of K8s cause the loss of cache
sql tables?*
*How do you
> Is this maybe the case? This policy of K8s cause the loss of cache sql tables?
In the case of in-memory cluster, simultaneous restart of all nodes
could be a reason. Also, you could look for the log messages about
changing of cluster topology and errors.
As I see from the attached picture, you
Ok,
I will remove the backup configuration setting of cache. But about you said,
*In the case of in-memory cluster, simultaneous restart of all nodescould
be a reason. Also, you could look for the log messages aboutchanging of
cluster topology and errors.*
For the above case, what do you
You need to find out what the problem is before anyone can make a
recommendation. Why are your nodes restarting?
> On 26 Apr 2023, at 12:34, Abhishek Ubhe wrote:
>
> Ok,
> I will remove the backup configuration setting of cache. But about you said,
>
> In the case of in-memory cluster,
Igniters! The call for speakers for the virtual Ignite Summit 2023[1] is
closing in 5 days! That's the last call.
Ignite Summit will be delivered virtually *on June 6th*; attendance is
free.
We are seeking technical content from in-memory computing practitioners:
- An Ignite user story
- An
Hi Pavel,
We have implemented custom external cache store. We are running three
nodes as server nodes with external cache store implemented. Now if
we start a server with clientmode = true ( thick client) and do some
cache operations will external cache store
External cache store will work in any case - server, thick client, thin
client.
On Wed, Apr 26, 2023 at 4:05 PM satyajit.mandal.barclays.com via user <
user@ignite.apache.org> wrote:
>
>
> Hi Pavel,
>
>
>
> We have implemented custom external cache store. We are running
> three nodes