Re: GridGain Web Console is available free of charge for Apache Ignite

Hi Denis/Alexey, We have found few more vulnerabilities in Gridgain Web console and due to which we can't deploy it in production as it does not comply with FedRAMP certification. Can you please provide us the contact where we can send the detailed vulnerability report and help your team to find

Re: Partition/Fault tolerance and availability of Apache Ignite

Fault_tolerance.zip Hi Ilya, Thank you for your reply, I have attached the logs of the coordinator(S1) and S3. During the demonstration, I killed S2. I do not have a partition loss policy which means by default

Re: Failed to load bean in application context [beanName=dataSource] in ignite.Spring bean doesn't exist

Check a series of videos "Ignite Web Console - Automatic RDBMS Integration" showing how to import an RDBMS schema and generate code/configuration templates with Web Console: https://ignite.apache.org/screencasts.html - Denis On Sun, Feb 2, 2020 at 11:30 AM nithin91 <

Re: Ignite swap space

Swapping can come handy if a cluster node reaches its maximum memory capacity and, instead of failing with an out-of-memory exception, you can keep it alive by swapping out data before the cluster is scaled out. Once you add a new cluster node, the data will be rebalanced and the first node will

Re: DataStreamer as a Service

Ilya, I don't quite understand why data streamer is not suitable as a long-running solution. Please don't mislead, otherwise, list out specific limitations. I don't see anything wrong by having an opened data streamer that transfer data to Ignite in real-time. Narges, if the streamer crashes

Upcoming Ignite events in the US and India in February

Ignite community members, If you live nearby Chicago, Boston, San Francisco or Bengaluru (India) area visit our upcoming meetups and conference talks in those cities: https://ignite.apache.org/events.html Some of the community members are planning webinars in February and they will be announced

Offheap memory consumption + enabled persistence

Hi! Problem I've noticed some weird behavior while working with enabled persistence (native storage): I put some amount of entries to the cluster and delete them afterwards. When I use the same set of keys each time, I see that *DataRegionMetrics.getOffheapUsedSize* reaches some limit and don't

Re: "Adding entry to partition that is concurrently evicted" error

Thanks Andrei. Looking at my exception (see below), it seem like it is related to https://issues.apache.org/jira/browse/IGNITE-11620 in that it occurred while expiration was going on. 1. As a workaround, would it be valid to increase my ttl to reduce the possibility of this occurring ? 2.

Page size for large objects

Hi! As I got from the documentation, DataStorageConfiguration "pageSize" parameter have to be adjusted when we have a lot of big objects. 1) How to find out actual object size? I've accomplished it with *((BinaryObjectImpl)ignite.binary().toBinary(myObject)).length()*, but not sure whether it is

Re: Different data regions on nodes

Example as code: package com.test.ignite.dataregions; import org.apache.ignite.Ignite; import org.apache.ignite.Ignition; import org.apache.ignite.cache.CacheMode; import org.apache.ignite.configuration.CacheConfiguration; import org.apache.ignite.configuration.DataRegionConfiguration; import

Different data regions on nodes

Hi there! Is it allowed to have different data regions on server nodes? Example definition For instance, I want to have the following cluster: 1) server node #1 with data region "region1" 2) server node #2 with data regions "region1" and "region2" 3) server node #3 with data regions "region1"

Re: DataStreamer as a Service

Hello! I think these benefits are imaginary. You will have to worry about service more, rather about data streamer which may be recreated at any time. Regards, -- Ilya Kasnacheev пн, 3 февр. 2020 г. в 16:58, narges saleh : > Thanks Ilya. > I have to listen to these burst of data which

Re: Latest behaviour for write-behind cache on node crash

There is a ticket opened for this for some 4+ years https://issues.apache.org/jira/browse/IGNITE-1897 Since Ignite got its own native persistence implementation some years after the ticket was opened, chances that 3rd party persistence write behind failover gets implemented any time soon seem

Re: DataStreamer as a Service

Thanks Ilya. I have to listen to these burst of data which arrive every few seconds meaning an almost constant bursts of data from different data sources. The main reason that the services grid is appealing to me is its resiliency; I don't have to worry about it. With the client side streamer, I

Re: JVM Crashing with SegFault on org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write0

Hello! The only thing that stands off is that you have very deep object nesting, of level 12. Maybe it causes some very rare issue, I recommend trying to see if you will have this problem with flatter objects. This is a long shot, since we have not seen crashes like this one. Regards, -- Ilya

Re: Query execution is too long issue!

Hello! What happens if you do COUNT(*) instead? I think we have some specific optimizations for this case. Regards, -- Ilya Kasnacheev ср, 29 янв. 2020 г. в 12:28, rssah <77adity...@gmail.com>: > When querying via some java application and if the topology is in such a > way > that two

Re: Latest behaviour for write-behind cache on node crash

Hello! There is no failover for write-behind, it is lost if node is stopped abruptly. Regards, -- Ilya Kasnacheev пт, 31 янв. 2020 г. в 07:03, crypto_ricklee : > Dear all, > > I'm trying to get Ignite as a read-through/write-behind cache on top of > postgres. If I have 2 nodes setup

Re: exposing Ignite cluster health status in microservices

Hello! I think you can use either JMX beans or lifecycle listener. How to act on either one, depends on your use case. Regards, -- Ilya Kasnacheev пт, 31 янв. 2020 г. в 09:43, Kamlesh Joshi : > Hi Team, > > > > Is there any sophisticated way to check if Ignite cluster is Up and > Running

Re: Ignite swap space

Hello! I recommend using native persistence in this case. Regards, -- Ilya Kasnacheev пт, 31 янв. 2020 г. в 09:07, ashishb888 : > Thank you Evgenii! > > I can understand that enabling swap may decrease the performance. > Keeping in that mind I wanted to see what actually happens after

Re: DataStreamer as a Service

Hello! I don't see why you would deploy it as a service, sounds like you will have to send more data over network. If you have to pull batches in, then service should work. I recommend re-acquiring data streamer for each batch. Please note that Data Streamer is very scalable, so it is preferred

Re: DataStreamer as a Service

Hi Ilya The data comes in huge batches of records (each burst can be up to 50-100 MB, which I plan to spread across multiple streamers) so, the streamer seems to be the way to go. Also, I don't want to establish a JDBC connection each time. So, if the streamer is the way to go, is it feasible to

Re: Ignite AtomicLong

Hello! It uses a cache under the hood. I don't think it will throw TransactionRollbackException since it operates on ATOMIC cache. Regards, -- Ilya Kasnacheev пт, 31 янв. 2020 г. в 10:37, ashishb888 : > How does AtomicLong work? > Does it throws TransactionRollbackException? > > BR, >

Re: Failed to load bean in application context [beanName=dataSource] in ignite.Spring bean doesn't exist

Hello! You have to define your Oracle Data Source in XML files of all your instances (or at least all server nodes). There are other approaches, but this one is most straightforward. Regards, -- Ilya Kasnacheev вс, 2 февр. 2020 г. в 22:30, nithin91 <

Re: Table not found error while executing sql fields query API

Hello! Please show full configuration of your caches. It is possible that you have configured cache store but did not configure any indexing. Regards, -- Ilya Kasnacheev вс, 2 февр. 2020 г. в 22:48, nithin91 < nithinbharadwaj.govindar...@franklintempleton.com>: > Hi , > > We are doing a

Re: Class loader

Hi! Yes, that should do the trick, I will have a look at it. Thanks. Den 2020-02-03 kl. 12:05, skrev Ilya Kasnacheev: Hello! We have a thing calles URI deployment: https://apacheignite.readme.io/docs/deployment-spi It allows you to specify location to be scanned at regular intervals, if

Re: DataStreamer as a Service

Hello! Contrary to its name, data streamer is not actually suitable for long-lived, low-intensity streaming. What it's good for is burst load of large number of data in a short period of time. If your data arrives in large batches, you can use Data Streamer for each batch. If not, better use

Re: DataStreamer as a Service

Hi, But services are by definition long lived, right? Here is my layout: The data is continuously generated and sent to the streamer services (via JDBC connection with set streaming on option), deployed, say, as node singleton (actually deployed also as microservices) to load the data into the

Re: Exception when joining a data node

Hello! I think you should completely wipe persistence on "newly joining node" and re-join it. Regards, -- Ilya Kasnacheev пт, 31 янв. 2020 г. в 16:54, krkumar24061...@gmail.com < krkumar24061...@gmail.com>: > Sorry. I think I did not phrase the question properly. I stopped the ignite > with

Re: Exception thrown in K8S deployment

Hello Isuranga, I can see you are using 2.5.0 in your attempt to start a cluster, I would recommend to try the latest available version, that would be 2.7.6. Please if that is possible, try to provide full logs from cluster nodes instead of screenshots and their configurations, it is extremely

Re: Class loader

Hello! We have a thing calles URI deployment: https://apacheignite.readme.io/docs/deployment-spi It allows you to specify location to be scanned at regular intervals, if there are any new JARs they will be reloaded, with versioning support. Sounds like the exact thing that you are describing.

Re: DataStreamer as a Service

Hello! It is not recommended to have long-lived data streamers, it's best to acquire it when it is needed. If you have to keep data streamer around, don't forget to flush() it. This way you don't have to worry about its queue. Regards, -- Ilya Kasnacheev пн, 3 февр. 2020 г. в 13:24, narges

Re: @SpringResource not injected

Hello! You have to specify Spring factory when starting Ignite node for injection to work. For that, you should start your node with IgniteSpring.start(cfg, ApplicationContext) methods. If that does not work, please provide a small reproducer project so that we could check. Regards, -- Ilya

Re: Partition/Fault tolerance and availability of Apache Ignite

Hello! Can you please show more logs/full stack trace? Data Streamer is not especially fault tolerant, but it should survive a server node leaving. How many backups do you have? What is partition loss policy? Regards, -- Ilya Kasnacheev пт, 31 янв. 2020 г. в 11:02, userx : > Hi team, > > I

Re: DataStreamer as a Service

Hi, My specific question/concern is with regard to the state of the streamer when it run as a service, i.e. when it crashes and it gets redeployed. Specifically, what happens to the data? I have a similar question with regard to the state of a continuous query when it is deployed as a service,

Ignite ML - Weka integration?

Hi Ignite-ML Team, I have recently discovered WEKA - a Java ML workbench and library from the University of Waikato. I have observed that Ignite-ML is developing quickly in it's computational capabilities, but is lacking a 'workbench environment' for interactive data-science workflows.