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 <abhishekubhe0...@gmail.com> wrote: > > 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 nodes > could be a reason. Also, you could look for the log messages about > changing of cluster topology and errors. > > For the above case, what do you suggest I should do? > > On Wed, Apr 26, 2023 at 4:23 PM Ilya Shishkov <shishkovi...@gmail.com > <mailto:shishkovi...@gmail.com>> wrote: >> > 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 start Ignite embedded into the >> code, but it is unclear how you get the 'null' value for the ignite >> variable. Also, for replicated cache you should not set backups >> number, because all partitions of replicated cache are stored in each >> node of the cluster. >> >> >> ср, 26 апр. 2023 г. в 12:55, Abhishek Ubhe <abhishekubhe0...@gmail.com >> <mailto:abhishekubhe0...@gmail.com>>: >> > >> > 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 get "instance of Ignite"? -> >> > >> > >> > >> > >> > On Wed, Apr 26, 2023 at 2:40 PM Ilya Shishkov <shishkovi...@gmail.com >> > <mailto:shishkovi...@gmail.com>> wrote: >> >> >> >> 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 query. >> >> >> >> >> >> It looks like all cluster nodes have failed or restarted. >> >> >> >> >> >>> I am getting a null instance of ignite. I assume that I am unable to >> >>> connect to the live instance running on that node. >> >> >> >> >> >> How do you get "instance of Ignite"? >> >> >> >> Have you deployed the nodes as described in these instructions [1-3]? >> >> >> >> https://ignite.apache.org/docs/latest/installation/kubernetes/amazon-eks-deployment.html >> >> https://ignite.apache.org/docs/latest/installation/kubernetes/azure-deployment.html >> >> https://ignite.apache.org/docs/latest/installation/kubernetes/gke-deployment.html >> >> >> >> >> >> >> >> ср, 26 апр. 2023 г. в 09:42, Abhishek Ubhe <abhishekubhe0...@gmail.com >> >> <mailto:abhishekubhe0...@gmail.com>>: >> >>> >> >>> 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 using -java commands. >> >>> In that routine after node started, I created the above CacheTable on >> >>> the node and loaded data from hbase into the cache.table. >> >>> 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. >> >>> Now I am getting a table not found exception from API request for >> >>> fetching using ignite sql query. >> >>> And also I tried to recreate the same cache using a regular java API >> >>> script and run on that K8s pod where ignite is running >> >>> I am getting a null instance of ignite. I assume that I am unable to >> >>> connect to the live instance running on that node. >> >>> >> >>> Please help me with this issue and suggest any things I need to do and >> >>> test out. >> >>> >> >>> On Thu, Apr 20, 2023 at 1:52 PM Stephen Darlington >> >>> <stephen.darling...@gridgain.com >> >>> <mailto:stephen.darling...@gridgain.com>> wrote: >> >>>> >> >>>> In sqlline, you can type “!tables” (no quotes) to list all the tables. >> >>>> In general, the schema is the cache name and the table is the value >> >>>> type name, so you would need to write "select * from >> >>>> CACHE_NAME.HbaseTableType". >> >>>> >> >>>> On 20 Apr 2023, at 06:38, Abhishek Ubhe <abhishekubhe0...@gmail.com >> >>>> <mailto:abhishekubhe0...@gmail.com>> wrote: >> >>>> >> >>>> Hello, >> >>>> >> >>>> I am facing the issue as below : >> >>>> >> >>>> I have created an ignite cache SQL table through java API. >> >>>> Data loaded from HBase in the table after creating it.(loading means >> >>>> just fetched and inserted in ignite). >> >>>> Now when I was trying to fetch data from the sql table I created I am >> >>>> getting Failed to parse query and table not found exception. >> >>>> For more confirmation I connected to the ignite shell and checked the >> >>>> list of tables. I get the above created table in the list. I can see it >> >>>> exactly created there by the same name. >> >>>> But when I fire my query on the table I get Error of failing to parse >> >>>> the query and Table not found. >> >>>> >> >>>> I did not understand the above scenario. Please help me with this >> >>>> issue. Please check out the attached screenshot for reference. >> >>>> >> >>>> >> >>>> -- >> >>>> Regards, >> >>>> Abhishek Ubhe >> >>>> >> >>>> <Screenshot from 2023-04-19 18-50-23.png> >> >>>> >> >>>> >> >>> >> >>> >> >>> -- >> >>> Regards, >> >>> Abhishek Ubhe >> >>> >> > >> > >> > -- >> > Regards, >> > Abhishek Ubhe >> > > > > -- > Regards, > Abhishek Ubhe >
