Re: Diagrams on your website

I think they have drawn it with their hands. On Mon, Apr 29, 2019 at 1:45 PM Johannes Lichtenberger < johannes.lichtenber...@unitedplanet.com> wrote: > Hi, > > for instance the diagrams here: > https://apacheignite.readme.io/docs/memory-architecture > > Thanks and kind regards > > johannes > On

Re: Remote debugging

: >https://apacheignite-sql.readme.io/docs/performance-and-debugging >- Ignite console: console.gridgain.com > > -- > Denis > > On Wed, Jan 2, 2019 at 5:49 AM Lokesh Sharma > wrote: > >> Is there a way to query Ignite database that is deployed remotely? >>

Remote debugging

Is there a way to query Ignite database that is deployed remotely? I use H2 Debug Console locally but this doesn't work for remote purposes.

Re: Ignite complains for low heap memory

Thanks! It works. On Wed, Oct 17, 2018 at 4:46 PM Stanislav Lukyanov wrote: > Put your -X* options before -jar. That’s how java command line works. > > > > Stan > > > > *From: *Lokesh Sharma > *Sent: *17 октября 2018 г. 14:08 > *To: *user@ignite.apache.org

Re: Ignite complains for low heap memory

I get the same output in the logs when I run the application with Xms set to 2 GB. I ran this command: java -jar target/cm.jar -Xms2024m -Xmx4024m On Wed, Oct 17, 2018 at 4:26 PM aealexsandrov wrote: > Hi, > > The heap metrics that you see in topology message shows the max heap value > that

Re: Ignite complains for low heap memory

*Typo Correction: The later heap size is 2.6 GB not 2 GB. On Wed, Oct 17, 2018 at 3:53 PM Lokesh Sharma wrote: > When Ignite boots up, it initially complains that only "188 MB is > available": > > 2018-10-17 15:44:12.295 WARN 151

Ignite complains for low heap memory

When Ignite boots up, it initially complains that only "188 MB is available": 2018-10-17 15:44:12.295 WARN 15129 --- [pub-#22%cm%] > o.apache.ignite.internal.GridDiagnostic : Initial heap size is 188MB > (should be no less than 512MB, use -Xms512m -Xmx512m). > [15:44:12] Initial heap size

Re: Problems are enabling Ignite Persistence

are still available. > Note that it will only work if you keep persistence directory intact > between runs. > I'm also not completely sure whether it will work with one node only. > > Regards, > -- > Ilya Kasnacheev > > > пт, 28 сент. 2018 г. в 17:33, Lokesh Sharma : &

Re: Problems are enabling Ignite Persistence

Hi Thanks for looking into this. > First, I had to change h2 version dependency from 1.4.197 to 1.4.195 - > maybe > this is because I have later snapshot of Apache Ignite compiled. The version is already 1.4.195. Second, I had to activate the cluster! You have to activate persistent >

Re: Problems are enabling Ignite Persistence

> > Could you try to send minimalistic reproducer that > shows issue on clean setup? I have reproduced a minimal project that shows this behaviour. Here it is https://bitbucket.org/lokesh_blue/bugdemo/src/master/ It's a simple application. It should execute function "test" when ran. See (

Problems are enabling Ignite Persistence

I enabled Ignite Persistence. Following is my configuration: //New Data Region > DataStorageConfiguration storageCfgPersistence = new > DataStorageConfiguration(); > DataRegionConfiguration regionCfg = new DataRegionConfiguration(); >

Re: AFTER_NODE_START event

Great. Thank you for looking into it. On Mon, Sep 10, 2018, 9:11 PM Maxim.Pudov wrote: > Hello! > The answer is yes. It is safe to subscribe to AFTER_NODE_START. > I've just checked the sequence of events happening during the node startup > and org.apache.ignite.events.EventType#EVT_NODE_JOINED

AFTER_NODE_START event

I require a record to be present in the ignite database all the time. For this I have written a function like following: > > @PostConstruct > public void createRecordIfNotPresent() { > if (entityRepository.findById(1) == null) { > createRecord() > } > } I have added

Re: Execute IgniteRunnable in all Ignite nodes?

Many thanks! On Wed, Sep 5, 2018, 8:08 PM Ilya Kasnacheev wrote: > Hello! > > ignite.compute().broadcast() should do. > > Regards, > -- > Ilya Kasnacheev > > > ср, 5 сент. 2018 г. в 17:31, Lokesh Sharma : > >> During some events I want to run

Execute IgniteRunnable in all Ignite nodes?

During some events I want to run a piece of code at all nodes of Ignite. Is it possible? I know, its possible to run a Runnable in exactly any one of the nodes using exec.submit(new IgniteRunnable() { @Override public void run() { System.out.println(">>> Printing '" + word + "' on

Re: Is Pagination not supported in Ignite Spring data?

LIMIT in ignite SQL queries. > > Thanks, > Prasad > > On Tue, Sep 4, 2018 at 4:22 PM Lokesh Sharma > wrote: > >> Pagination works in Spring Data with following declaration in >> EntityRepository.java >> >> Page findAllByOrderById(Pageable pa

Is Pagination not supported in Ignite Spring data?

Pagination works in Spring Data with following declaration in EntityRepository.java Page findAllByOrderById(Pageable pageable); But this produces error in Ignite: java.lang.ClassCastException: com.project.common.igniteserver.model.Entity > cannot be cast to org.springframework.data.domain.Page

Re: What happens during network failure?

Luqman, I understand what you mean now. I need to use a SegmentationResolver which is implemented in your plugin which will generate EVT_NODE_SEGMENTED and in turn restart the nodes which are in invalid segments. Many thanks for writing the plugin :D On Fri, Aug 31, 2018 at 6:17 PM Lokesh Sharma

Re: What happens during network failure?

Luqman, if I subscribe to EVT_NODE_FAILED, how do I figure out which node to restart? For example in case of 2 nodes separating from each other, both would receive that event. On Thu, Aug 30, 2018 at 4:30 AM luqmanahmad wrote: > Lokesh, looking at the javadocs of [1] you can subscribe for >

Re: How to run a job every 5 seconds in Ignite

I managed to run the task every x seconds using an infinite loop though. "deployClusterSingleton" was the key to make it work. Many thanks. On Thu, Aug 30, 2018 at 12:57 PM Lokesh Sharma wrote: > That didn't help because extended syntax is not for running task every x > secon

Re: How to run a job every 5 seconds in Ignite

extended cron syntax implemented by Ignite [1]. > > [1] > https://apacheignite.readme.io/docs/cron-based-scheduling#section-syntax-extension > > > 2018-08-28 10:51 GMT+03:00 Lokesh Sharma : > >> Is it possible to run the job every few seconds? As far as I know, cron >>

Re: What happens during network failure?

Thanks for the docs. The docs says "EVT_NODE_SEGMENTED" is Generated when node determines that it runs in invalid network segment. But when I disconnected 1 node from a cluster of 2 nodes, none of the 2 nodes generated that event. They both released only "EVT_NODE_FAIL" event. On Wed, Aug 29,

Re: What happens during network failure?

Thanks Luqman This is what I'm looking for. I'm stuck on one thing though. What's the difference between EVT_NODE_FAIL and EVT_NODE_SEGMENTED? I want to restart the detached node. I created 2 nodes to experiment. I detached them and both the nodes received EVT_NODE_FAIL but none of them received

Re: What happens during network failure?

ead.run(IgniteSpiThread.java:62) > [ignite-core-2.7.0-SNAPSHOT.jar!/:2.7.0-SNAPSHOT] Any idea how to fix this? I also tried with the flag "-Djava.net.preferIPv4Stack=true" but it didn't make a difference. > On Tue, Aug 28, 2018 at 9:04 PM Lokesh Sharma wrote: > I mainly wan

Re: What happens during network failure?

I mainly want to know whether the detached need would join the cluster automatically after the network is back or not? On Tue, Aug 28, 2018, 8:09 PM Lokesh Sharma wrote: > What is the expected behaviour of Ignite when a node is unreachable from > other nodes of the cluster due to *n

What happens during network failure?

What is the expected behaviour of Ignite when a node is unreachable from other nodes of the cluster due to *network failure *(and not due to node failure), and after a while the node is again accessible from the cluster? In other words, one node gets dropped from the cluster due to network failure

Re: How to run a job every 5 seconds in Ignite

Is it possible to run the job every few seconds? As far as I know, cron API doesn't support scheduling in seconds. On Tue, Aug 28, 2018 at 11:27 AM Lokesh Sharma wrote: > This is what I was looking for. Many thanks! > > On Mon, Aug 27, 2018 at 3:01 PM Evgenii Zhuravlev < &

Re: How to run a job every 5 seconds in Ignite

ngleton to make sure that you will have 1 instance of Service in > cluster. Inside this service you can use ignite-scheduler: > https://apacheignite.readme.io/docs/cron-based-scheduling, it has > cron API. > > Evgenii > > пн, 27 авг. 2018 г. в 9:16, Lokesh Sharma : &g

How to run a job every 5 seconds in Ignite

I'm using Ignite with Spring Boot. Is there a way to run a job every 5 seconds on exactly one node of the cluster (which could be any node)? Thank You

Re: Persistence with Spring Data

, persistent > and non-persistent: > > https://apacheignite.readme.io/docs/memory-configuration#section-data-regions > > Regards, > > -- > Ilya Kasnacheev > > 2018-08-10 16:09 GMT+03:00 Lokesh Sharma : > >> Hi all >> >> Is it possible to have persiste

Persistence with Spring Data

Hi all Is it possible to have persistence enable for just a single table when using Ignite through Spring Data rather than having it enabled for all the tables?

Re: Ignite Spring Data 2.0 not working with Spring Boot 2

I just realized that the problem wasn't with logging but rather the annotations like "PostConstruct" and "Scheduled" are not working with Ignite Spring Data_2.0. I've created an issue here https://issues.apache.org/jira/browse/IGNITE-9187 On Fri, Aug 3, 2018 at 11:03 AM

Re: Ignite Spring Data 2.0 not working with Spring Boot 2

umentation: > https://apacheignite.readme.io/docs/logging > Choose a suitable logger and refer to a corresponding section of the docs. > > Denis > > чт, 2 авг. 2018 г. в 9:59, Lokesh Sharma : > >> (I'm sorry if I created this thread twice. Kindly delete the earlier one.) &

Ignite Spring Data 2.0 not working with Spring Boot 2

(I'm sorry if I created this thread twice. Kindly delete the earlier one.) I built the "ignite-spring-data_2.0" from source to run it with Spring Boot 2.0.2-RELEASE. The app is running fine but nothing is being logged in the console. Please help. Here's my code: