Random failure while data insertion in ignite cache

2023-07-14 Thread Abhishek Ubhe 
Hello,

I am facing an issue for putting data in ignite caches. I have checked from
start to end flow for data insertion but I haven't found anything here are
scenarios I have checked and I find issues in this way :


   1. I added logs at every step from object formation to insertion in
   cache.
   2. All logs are present there without a single error, as per flow
   defined.
   3. But still I am unable to fetch data from cache. It is not inserted in
   the cache.

*Note :  This issue is random and happened unexpectedly a few times in a
month. I was unable to reproduce this issue.*

*Please append for any suggestions or solutions.*
-- 
*Regards,*
*Abhishek Ubhe*

Re: Failed to parse query SQL table not found issue

2023-04-26 Thread Abhishek Ubhe 
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 suggest I should do?

On Wed, Apr 26, 2023 at 4:23 PM Ilya Shishkov 
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 :
> >
> > 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 
> 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  >:
> >>>
> >>> 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> 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 
> wrote:
> >>>>
> >>>> Hello,
> >>>>
> >>>> I am facing the issue as below :
> >>>>
> >>>> I h

Re: Failed to parse query SQL table not found issue

2023-04-26 Thread Abhishek Ubhe 
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"? -> *

[image: image.png]


On Wed, Apr 26, 2023 at 2:40 PM Ilya Shishkov 
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]?
>
>
>1.
>
> https://ignite.apache.org/docs/latest/installation/kubernetes/amazon-eks-deployment.html
>2.
>
> https://ignite.apache.org/docs/latest/installation/kubernetes/azure-deployment.html
>3.
>
> https://ignite.apache.org/docs/latest/installation/kubernetes/gke-deployment.html
>
>
>
> ср, 26 апр. 2023 г. в 09:42, Abhishek Ubhe :
>
>> 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> 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 
>>> wrote:
>>>
>>> Hello,
>>>
>>> I am facing the issue as below :
>>>
>>>1. I have created an ignite cache SQL table through java API.
>>>2. Data loaded from HBase in the table after creating it.(loading
>>>means just fetched and inserted in ignite).
>>>3. 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.
>>>    4. 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.
>>>5. 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*
>>>
>>> 
>>>
>>>
>>>
>>
>> --
>> *Regards,*
>> *Abhishek Ubhe*
>>
>>

-- 
*Regards,*
*Abhishek Ubhe*

Re: Failed to parse query SQL table not found issue

2023-04-26 Thread Abhishek Ubhe 
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> 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 
> wrote:
>
> Hello,
>
> I am facing the issue as below :
>
>1. I have created an ignite cache SQL table through java API.
>2. Data loaded from HBase in the table after creating it.(loading
>means just fetched and inserted in ignite).
>3. 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.
>4. 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.
>5. 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*
>
> 
>
>
>

-- 
*Regards,*
*Abhishek Ubhe*

JVM pause on Ignite kernal

2023-04-16 Thread Abhishek Ubhe 
Hello,

Getting below log often times on a ignite node which runs as a microservice
deployed on Kubernetes pod.

*org.apache.ignite.internal.IgniteKernal - Possible too long JVM pause: 803
milliseconds.*

   - I need to know when this log was printed and why?
   - What should I do to avoid it?
   - How monitor these nodes/ services to prevent JVM pause for future?




-- 
*Regards,*
*Abhishek Ubhe*

Regarding error : TcpCommunicationSpi - Failed to send message to remote node

2023-03-21 Thread Abhishek Ubhe 
)
~[ignite-core-2.10.0.jar:2.10.0]
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.sendReply(IgniteTxHandler.java:1573)
~[ignite-core-2.10.0.jar:2.10.0]
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processDhtTxPrepareRequest(IgniteTxHandler.java:1327)
~[ignite-core-2.10.0.jar:2.10.0]
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$400(IgniteTxHandler.java:135)
~[ignite-core-2.10.0.jar:2.10.0]
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$5.apply(IgniteTxHandler.java:244)
~[ignite-core-2.10.0.jar:2.10.0]
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$5.apply(IgniteTxHandler.java:242)
~[ignite-core-2.10.0.jar:2.10.0]
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1142)
~[ignite-core-2.10.0.jar:2.10.0]
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:591)
~[ignite-core-2.10.0.jar:2.10.0]
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:392)
~[ignite-core-2.10.0.jar:2.10.0]
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:318)
~[ignite-core-2.10.0.jar:2.10.0]
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109)
~[ignite-core-2.10.0.jar:2.10.0]
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308)
~[ignite-core-2.10.0.jar:2.10.0]
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1908)
~[ignite-core-2.10.0.jar:2.10.0]
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1529)
~[ignite-core-2.10.0.jar:2.10.0]
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$5300(GridIoManager.java:242)
~[ignite-core-2.10.0.jar:2.10.0]
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.execute(GridIoManager.java:1422)
~[ignite-core-2.10.0.jar:2.10.0]
at
org.apache.ignite.internal.managers.communication.TraceRunnable.run(TraceRunnable.java:55)
~[ignite-core-2.10.0.jar:2.10.0]
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:569)
~[ignite-core-2.10.0.jar:2.10.0]
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
~[ignite-core-2.10.0.jar:2.10.0]
at java.lang.Thread.run(Thread.java:750) [?:1.8.0_332]
Caused by: java.net.SocketTimeoutException
at sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:129) ~[?:1.8.0_332]
at
org.apache.ignite.spi.communication.tcp.internal.GridNioServerWrapper.createNioSession(GridNioServerWrapper.java:465)
~[ignite-core-2.10.0.jar:2.10.0]
... 30 more
Caused by: org.apache.ignite.IgniteCheckedException: Remote node does not
observe current node in topology : 6cc31b37-7870-413a-b75a-95b4371fc542
at
org.apache.ignite.spi.communication.tcp.internal.GridNioServerWrapper.createNioSession(GridNioServerWrapper.java:505)
~[ignite-core-2.10.0.jar:2.10.0]
... 30 more
-- 
*Regards,*
*Abhishek Ubhe*

Re: JmxExporter error while starting ignite node

2023-03-21 Thread Abhishek Ubhe 
Okay. Thanks.

On Wed, Mar 15, 2023 at 6:36 PM Вячеслав Коптилин 
wrote:

> Hello Abhishek,
>
> You don't need to register JmxSystemViewExporterSpi explicitly via
> configuration. This exporter implicitly enabled/registered on the startup
> Ignite node. That is the reason why you are getting: IgniteCheckedException:
> Duplicate SPI name (need to explicitly configure 'setName()' property):
> JmxSystemViewExporterSpi
>
> > SEVERE: JMX scrape failed: java.lang.IllegalArgumentException: Not an
> Attribute: javax.management.openmbean.TabularDataSupport Could you please
> provide a full stack trace?
>
> Thanks,
> S.
>
> ср, 15 мар. 2023 г. в 08:58, Abhishek Ubhe :
>
>> Hello,
>>
>> Getting below error while starting ignite node. Please check and suggest
>> any changes required.
>>
>> *After upgrading JMX to 18 I'm getting above error while starting ignite 
>> node.*
>>
>> SEVERE: JMX scrape failed: java.lang.IllegalArgumentException: Not an 
>> Attribute: javax.management.openmbean.TabularDataSupport
>>
>>
>> *Then by referring internet I make changes as below *
>>
>> SystemViewExporterSpi systemViewExporter = new JmxSystemViewExporterSpi();
>>  systemViewExporter.setExportFilter(i -> false);
>>  MetricExporterSpi metricExporter = new JmxMetricExporterSpi();
>>  metricExporter.setExportFilter(i -> false);
>>
>>
>> new IgniteConfiguration().setSystemViewExporterSpi(systemViewExporter)
>>  .setMetricExporterSpi(metricExporter)
>>
>>
>>
>> *Now I am getting below error :*
>>
>> 06:24:27.570 ERROR org.apache.ignite.internal.IgniteKernal - Failed to start 
>> manager: GridManagerAdapter [enabled=true, 
>> name=o.a.i.i.managers.systemview.GridSystemViewManager]
>> org.apache.ignite.IgniteCheckedException: Duplicate SPI name (need to 
>> explicitly configure 'setName()' property): JmxSystemViewExporterSpi
>>  at 
>> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:268)
>>  ~[ignite-core-2.14.0.jar:2.14.0]
>>  at 
>> org.apache.ignite.internal.managers.systemview.GridSystemViewManager.start(GridSystemViewManager.java:71)
>>  ~[ignite-core-2.14.0.jar:2.14.0]
>>  at 
>> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1766) 
>> ~[ignite-core-2.14.0.jar:2.14.0]
>>  at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:998) 
>> ~[ignite-core-2.14.0.jar:2.14.0]
>>  at 
>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1757)
>>  ~[ignite-core-2.14.0.jar:2.14.0]
>>  at 
>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1679)
>>  ~[ignite-core-2.14.0.jar:2.14.0]
>>  at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1121) 
>> ~[ignite-core-2.14.0.jar:2.14.0]
>>  at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:657) 
>> ~[ignite-core-2.14.0.jar:2.14.0]
>>  at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:579) 
>> ~[ignite-core-2.14.0.jar:2.14.0]
>>  at org.apache.ignite.Ignition.start(Ignition.java:328) 
>> ~[ignite-core-2.14.0.jar:2.14.0]
>>  at 
>> com.clouds.ignite.server.startup.IgniteClusterNode.ignite(IgniteClusterNode.java:51)
>>  ~[clouds-ignite-core-2.4.94_jmx.jar:?]
>>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
>> ~[?:1.8.0_171]
>>  at 
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>  ~[?:1.8.0_171]
>>  at 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>  ~[?:1.8.0_171]
>>  at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_171]
>>  at 
>> org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:154)
>>  ~[spring-beans-5.2.2.RELEASE.jar:5.2.2.RELEASE]
>>
>>
>> --
>> *Regards,*
>> *Abhishek Ubhe*
>>
>>

-- 
*Regards,*
*Abhishek Ubhe*

JmxExporter error while starting ignite node

2023-03-15 Thread Abhishek Ubhe 
Hello,

Getting below error while starting ignite node. Please check and suggest
any changes required.

*After upgrading JMX to 18 I'm getting above error while starting ignite node.*

SEVERE: JMX scrape failed: java.lang.IllegalArgumentException: Not an
Attribute: javax.management.openmbean.TabularDataSupport


*Then by referring internet I make changes as below *

SystemViewExporterSpi systemViewExporter = new JmxSystemViewExporterSpi();
systemViewExporter.setExportFilter(i -> false);
MetricExporterSpi metricExporter = new JmxMetricExporterSpi();
metricExporter.setExportFilter(i -> false);


new IgniteConfiguration().setSystemViewExporterSpi(systemViewExporter)
.setMetricExporterSpi(metricExporter)



*Now I am getting below error :*

06:24:27.570 ERROR org.apache.ignite.internal.IgniteKernal - Failed to
start manager: GridManagerAdapter [enabled=true,
name=o.a.i.i.managers.systemview.GridSystemViewManager]
org.apache.ignite.IgniteCheckedException: Duplicate SPI name (need to
explicitly configure 'setName()' property): JmxSystemViewExporterSpi
at 
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:268)
~[ignite-core-2.14.0.jar:2.14.0]
at 
org.apache.ignite.internal.managers.systemview.GridSystemViewManager.start(GridSystemViewManager.java:71)
~[ignite-core-2.14.0.jar:2.14.0]
at 
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1766)
~[ignite-core-2.14.0.jar:2.14.0]
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:998)
~[ignite-core-2.14.0.jar:2.14.0]
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1757)
~[ignite-core-2.14.0.jar:2.14.0]
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1679)
~[ignite-core-2.14.0.jar:2.14.0]
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1121)
~[ignite-core-2.14.0.jar:2.14.0]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:657)
~[ignite-core-2.14.0.jar:2.14.0]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:579)
~[ignite-core-2.14.0.jar:2.14.0]
at org.apache.ignite.Ignition.start(Ignition.java:328)
~[ignite-core-2.14.0.jar:2.14.0]
at 
com.clouds.ignite.server.startup.IgniteClusterNode.ignite(IgniteClusterNode.java:51)
~[clouds-ignite-core-2.4.94_jmx.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
~[?:1.8.0_171]
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
~[?:1.8.0_171]
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[?:1.8.0_171]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_171]
at 
org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:154)
~[spring-beans-5.2.2.RELEASE.jar:5.2.2.RELEASE]


-- 
*Regards,*
*Abhishek Ubhe*

Re: Unable to start Ignite server node through java API

2023-03-01 Thread Abhishek Ubhe 
Hello Gianluca,

Here I have attached a pom you can check.

I think It may be happening because of other dependencies of spark and
ignite-spark.

On Wed, Mar 1, 2023 at 7:00 PM Gianluca Bonetti 
wrote:

> Hello
>
> I only use:
>
>   
> org.apache.ignite
> ignite-core
> 2.14.0
>   
>
> Which brings in what is required and actually does NOT bring in H2,
> because it's not required any more.
>
> I guess you should fix your pom.xml, which I have no information about, as
> you didn't share.
>
> Cheers
> Gianluca
>
> On Wed, 1 Mar 2023 at 13:22, Abhishek Ubhe 
> wrote:
>
>> Okay, Can you suggest any changes in maven dependencies?
>>
>> On Wed, Mar 1, 2023 at 2:07 PM Gianluca Bonetti <
>> gianluca.bone...@gmail.com> wrote:
>>
>>> Hello
>>>
>>> It's very strange that this method does not exist in the H2 library.
>>> Can you please check you're not including the H2 library twice?
>>> For what I know, Ignite works with h2-1.4.197.jar which is included in
>>> the last bundle.
>>> I think you are including a newer version instead, or aside.
>>>
>>> Cheers
>>> Gianluca
>>>
>>> On Wed, 1 Mar 2023 at 06:43, Abhishek Ubhe 
>>> wrote:
>>>
>>>> Hello,
>>>>
>>>> I am unable to start ignite server node with default configurations.
>>>> Getting below error
>>>>
>>>> Exception in thread "main" java.lang.NoSuchMethodError:
>>>> org.apache.ignite.internal.processors.cache.persistence.tree.io.PageIO.registerH2(Lorg/apache/ignite/internal/processors/cache/persistence/tree/io/IOVersions;Lorg/apache/ignite/internal/processors/cache/persistence/tree/io/IOVersions;)V
>>>>
>>>> *stacktrace :* at
>>>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.(IgniteH2Indexing.java:197)
>>>> at java.lang.Class.forName0(Native Method)
>>>> at java.lang.Class.forName(Class.java:264)
>>>> at
>>>> org.apache.ignite.internal.util.IgniteUtils.inClassPath(IgniteUtils.java:1753)
>>>> at
>>>> org.apache.ignite.internal.IgniteComponentType.inClassPath(IgniteComponentType.java:172)
>>>> at
>>>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1999)
>>>> at
>>>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1758)
>>>> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1143)
>>>> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:663)
>>>> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589)
>>>> at org.apache.ignite.Ignition.start(Ignition.java:328)
>>>>
>>>>
>>>> Please help with this and let me know why this error is getting and how
>>>> I can avoid it in future.
>>>> My API :
>>>> IgniteConfiguration cfg = new IgniteConfiguration();
>>>> cfg.setClientMode(false);
>>>>
>>>> cfg.setWorkDirectory("/home/developers/apache_ignite_home/apache-ignite-2.14.0-bin/work");
>>>>  Ignite ignite = Ignition.start(cfg);
>>>>
>>>> version using : 2.14.0
>>>> --
>>>> *Regards,*
>>>> *Abhishek Ubhe*
>>>>
>>>>
>>
>> --
>> *Regards,*
>> *Abhishek Ubhe*
>>
>>

-- 
*Regards,*
*Abhishek Ubhe*
http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd;>
  4.0.0

  com
  clouds-ignitesparksql
  0.0.7
  jar

  clouds-ignitesparksql
  http://maven.apache.org

  
  
  
		UTF-8
		1.10.94

	

	
		
			MavenCentral
			https://repo.maven.apache.org/maven2/
		

		
			central
			http://maven.clouzerindia.com:8081/artifactory/plugins-release-local/
		
	


	
		
			central
			nodedev-releases
			http://maven.clouzerindia.com:8081/artifactory/plugins-release-local/
		
	

	
   
			com.clouds
			clouds-core
			${clouds-core.version}
			

	com.clouds
			clouds-ignite-core

			
		
		
		 
		com
		  clouds-ignite-cluster
		  IGN_0.2.0
		  

	org.apache.ignite
			ignite-core

			
		  
		  
		  
	org.apache.ignite
	ignite-core
	2.14.0
	
		  
		  
			
		org.apache.ignite
ignite-spark
2.4.0


	org.apache.ignite
			ignite-core

			
			
		  
		  
		  
  org.apache.spark
   spark-core_2.12
   3.1.1
  			
  			
 			 
org.apache.spark
   spark-sql_2.12
3.1.1
  			
  			

  junit
  junit
  3.8.1
  test

Re: Unable to start Ignite server node through java API

2023-03-01 Thread Abhishek Ubhe 
Okay, Can you suggest any changes in maven dependencies?

On Wed, Mar 1, 2023 at 2:07 PM Gianluca Bonetti 
wrote:

> Hello
>
> It's very strange that this method does not exist in the H2 library.
> Can you please check you're not including the H2 library twice?
> For what I know, Ignite works with h2-1.4.197.jar which is included in the
> last bundle.
> I think you are including a newer version instead, or aside.
>
> Cheers
> Gianluca
>
> On Wed, 1 Mar 2023 at 06:43, Abhishek Ubhe 
> wrote:
>
>> Hello,
>>
>> I am unable to start ignite server node with default configurations.
>> Getting below error
>>
>> Exception in thread "main" java.lang.NoSuchMethodError:
>> org.apache.ignite.internal.processors.cache.persistence.tree.io.PageIO.registerH2(Lorg/apache/ignite/internal/processors/cache/persistence/tree/io/IOVersions;Lorg/apache/ignite/internal/processors/cache/persistence/tree/io/IOVersions;)V
>>
>> *stacktrace :* at
>> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.(IgniteH2Indexing.java:197)
>> at java.lang.Class.forName0(Native Method)
>> at java.lang.Class.forName(Class.java:264)
>> at
>> org.apache.ignite.internal.util.IgniteUtils.inClassPath(IgniteUtils.java:1753)
>> at
>> org.apache.ignite.internal.IgniteComponentType.inClassPath(IgniteComponentType.java:172)
>> at
>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1999)
>> at
>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1758)
>> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1143)
>> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:663)
>> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589)
>> at org.apache.ignite.Ignition.start(Ignition.java:328)
>>
>>
>> Please help with this and let me know why this error is getting and how I
>> can avoid it in future.
>> My API :
>> IgniteConfiguration cfg = new IgniteConfiguration();
>> cfg.setClientMode(false);
>>
>> cfg.setWorkDirectory("/home/developers/apache_ignite_home/apache-ignite-2.14.0-bin/work");
>>  Ignite ignite = Ignition.start(cfg);
>>
>> version using : 2.14.0
>> --
>> *Regards,*
>> *Abhishek Ubhe*
>>
>>

-- 
*Regards,*
*Abhishek Ubhe*

Unable to start Ignite server node through java API

2023-02-28 Thread Abhishek Ubhe 
Hello,

I am unable to start ignite server node with default configurations.
Getting below error

Exception in thread "main" java.lang.NoSuchMethodError:
org.apache.ignite.internal.processors.cache.persistence.tree.io.PageIO.registerH2(Lorg/apache/ignite/internal/processors/cache/persistence/tree/io/IOVersions;Lorg/apache/ignite/internal/processors/cache/persistence/tree/io/IOVersions;)V

*stacktrace :* at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.(IgniteH2Indexing.java:197)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at
org.apache.ignite.internal.util.IgniteUtils.inClassPath(IgniteUtils.java:1753)
at
org.apache.ignite.internal.IgniteComponentType.inClassPath(IgniteComponentType.java:172)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1999)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1758)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1143)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:663)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589)
at org.apache.ignite.Ignition.start(Ignition.java:328)


Please help with this and let me know why this error is getting and how I
can avoid it in future.
My API :
IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setClientMode(false);
cfg.setWorkDirectory("/home/developers/apache_ignite_home/apache-ignite-2.14.0-bin/work");
 Ignite ignite = Ignition.start(cfg);

version using : 2.14.0
-- 
*Regards,*
*Abhishek Ubhe*

Re: random scenario of insertion operations failed.

2023-02-16 Thread Abhishek Ubhe 
Hello,

I am facing an issue while inserting data in ignite cache.

Details : I have started ignite server nodes through kubernetes pod and
using microservice architecture to process data internally. Some times
randomly some requests for ignite insertions are not processed
successfully. There is no specific error or delay logs to define this
issue. No explanation found till now for me.

I have checked below things :


   1. Checked all configurations for Ignite as well as *write behind
   database storage Apache Hbase*
   2. *Last log for before PUT in* cache is present.
   3. Still not inserted without any error & delays.
   4. I have also checked if other technology level issues are present on
   the server at that specific time.


*Special Note *: Above issue is produced randomly for my server and also
resolved automatically after some time. I am using* Ignite 2.10.0*

-- 
*Regards,*
*Abhishek Ubhe*