Cache is too slow

Hi,We have setup 3 node cluster with Replicated caches. Ignite starts with our JAX-RS servvices on Liberty server.We have exposed an API and reading the values from cache(no business logic). Just read it from Ignite cache and return it and it is taking more than 6 seconds. We had run load test

ClusterTopologyServerNotFoundException

Hi,We have setup 3 node cluster on Linux server with 2 core CPU and 8 GB RAM. We have configured Ignite persistence and replicated caches.Please find attached configuration in the email. example-ignite-sample.xml

Re: 2.4.0 with Tomcat 7 and Java 9

I decided to do a quick test by taking Tomcat out of the equation and just launching Ignite from my home directory and got: WARNING: Illegal reflective access by org.apache.ignite.internal.util.GridUnsafe$2 (file:/home/eham/apache-ignite-fabric-2.4.0-bin/libs/ignite-core-2.4.0.jar) to field

IgniteClient dead because of "java.lang.OutOfMemoryError: Java heap space Failed to process selector key"

I have 2 node for server and 3 node for client, I've got this excpetion twice, why ?? 2018-03-31 10:09:07.933 | [grid-nio-worker-client-listener-0-#30%adminClient%] [ERROR] (Log4JLogger.java:495) Failed to process selector key [ses=GridSelectorNioSessionImpl [worker=ByteBufferNioClientWorker

Re: How to insert multiple rows/data into Cache once

Hi Andrey, I have similar requirement and I am using cache.putAll method to update existing entries or to insert new ones. I will be updating/inserting close to 3 million entries in one go. I am using wrte through approach to update/insert/delete the data in oracle tables. I am using cachestores

Re: 2.4.0 with Tomcat 7 and Java 9

Yes, thank you for the suggestion. We originally tried Tomcat 8.5 as our dev group was wanting JDK 9. However, the dev group ran into class loader issues with their app that they could not resolve by our product's release timeline, so we fell back to Tomcat 7 as JDK 9 looked supported and has

Re: 2.4.0 with Tomcat 7 and Java 9

I would still go for a higher tomcat version. > On 31. Mar 2018, at 00:26, Eric Ham wrote: > > From what I read on the changelog [1] they've been doing updates for Java 9 > since at least 7.0.70, with a lot of changes in 7.0.83 and they're now up to > 7.0.85. > > We've

Re: 2.4.0 with Tomcat 7 and Java 9

>From what I read on the changelog [1] they've been doing updates for Java 9 since at least 7.0.70, with a lot of changes in 7.0.83 and they're now up to 7.0.85. We've been running Tomcat 7 on JDK9 for over 3 months now with no other issues. [1]

Re: Upgrade from 2.1.0 to 2.4.0 resulting in error within transaction block

>From my reading of the javadoc of org.apache.ignite.IgniteCache, only methods that are inherited from javax.cache.Cache are transactional. So, get(..) and put(..) are transactional, but query(..) is not.. >From the javadoc...: Transactions Cache API supports transactions. You can group and set

Re: Failed to process selector key

Thank you for responding. No. It is definitely not fixed. Looking at all ERROR & WARN logging on the Remote Host mentioned in the `Failed to process selector key` message for a given Spike. ``` [2018-03-30T12:26:26,051Z](grid-nio-worker-tcp-comm-2-#43)([]) ERROR - TcpCommunicationSpi - Failed

Re: 2.4.0 with Tomcat 7 and Java 9

Tomcat 7 does not support JDK 9 > On 30. Mar 2018, at 18:30, Eric Ham wrote: > > I'm running Tomcat 7 with Oracle JDK 9.0.4 and am attempting to use web > session clustering based on the following pages [1] and [2] as I saw the > 2.4.0 release notes say Java 9 is now

Re: How to insert multiple rows/data into Cache once

Hi, Ignite has 2 JDBC drivers. 1. Client driver [1] starts client node (has all failover features) and you have to pass client node config in URL. 2. Thin Driver [2] that connect directly to one of Ignite server node. So, you need a first one to be able to use streaming mode. [1]

Re: Ignite Client Heap out of Memory issue

Hi Shawn, 1. Ignite use off heap to store cache entries. Client store no cache data. Cache in LOCAL mode can be used on client side, and it should use offheap of course. All data client retreive from server will be in offheap 2. It is not IgniteOutOfMemory error, but JVM OOM. So, try to

Re: Slow data load in ignite from S3

Hi, Possibly, storage is a bottleneck or checkpoint buffer is too large. Do you use Provissioned IOPS SSD? On Fri, Mar 30, 2018 at 3:32 PM, rahul aneja wrote: > Hi , > > We are trying to load orc data (around 50 GB) on s3 from spark using > dataframe API. It starts

Re: Failed to process selector key

Hi, Connection reset by peer means that remote node closes connection. Obviously, the reason may be in remote node logs. Is the issue solved? or Can you share full logs? On Fri, Mar 30, 2018 at 6:55 PM, Chris Berry wrote: > Sorry. > I should add. > This is a 36 Node

2.4.0 with Tomcat 7 and Java 9

I'm running Tomcat 7 with Oracle JDK 9.0.4 and am attempting to use web session clustering based on the following pages [1] and [2] as I saw the 2.4.0 release notes say Java 9 is now supported. I copied the following jars over for Tomcat to load: ignite-core-2.4.0.jar ignite-log4j-2.4.0.jar

Re: Failed to process selector key

Sorry. I should add. This is a 36 Node Compute Grid. And our Spikes are always preceded by: `ComputeTaskTimeoutCheckedExceptions` Although, these are clearly symptoms and not the ultimate cause. Thanks, -- Chris -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Failed to process selector key

Hello, We have a 36 Node Ignite Cluster in Production taking a relatively high volume of Requests (6-10M Requests/hour) In general, it behaves beautifully. But we see occasional Spikes in response time (1-2 per hour - affecting 1-6 Nodes) Overall, these affect a handful of Requests (8-10

Re: Baseline Topology and Node Failure

Hi Dave, Yes, it should be sufficient for apply a new baseline to remove\add\replace a node. "--baseline set ( | )" - set a new baseline and then trigger rebalance. You can achieve same with "--baseline remove" and then "--baseline add". This will trigger rebalance twice, but the first rebalance

Re: Hi is ignite have a plan for materialized view

Hi, Ignite has no supported view. We have no plans to add materialized view support in a meduim term perspective as it distributed implementation looks too complex and low performant. On Fri, Mar 30, 2018 at 9:51 AM, ??′ ?? wrote: > Hi >I wanna to use ignite like

Re: Running heavy queries on Ignite cluster on backing store directly without impacting the cluster

Hi Naveen, Ignite implements page memory concept since version 2.0 has been released. This means, Ignite reads page from disk if it is not loaded to memory and evict pages to disk to free memory. Page load and eviction work automatically. So, I can't understand what "feature like eviction" and

Re: Ignite cache get operation not working, client application stucks at the initializaiton

Hi Evgenii, Please find the logs. ignite-client-thread-dump.txt ignite-server-log.txt -- Sent from:

Re: Ignite cache get operation not working, client application stucks at the initializaiton

Unfortunately, there are no logs in your previous messages, could you please check why they were not attached? Evgenii 2018-03-30 16:24 GMT+03:00 Priyanka Shinde : > Thank You for the reply Evgenii. > > I have shared server logs and client thread dump in my earlier

Re: Ignite cache get operation not working, client application stucks at the initializaiton

Thank You for the reply Evgenii. I have shared server logs and client thread dump in my earlier message. I have tried to reproduce the similar use case in the sample project but not able to reproduce the exact scenario. I did not get any exception while running the sample project. But while

Slow data load in ignite from S3

Hi , We are trying to load orc data (around 50 GB) on s3 from spark using dataframe API. It starts fast with good write throughput and then after sometime throughput just drops and it gets stuck. We also tried changing multiple configurations , but no luck 1. enabling checkpoint write

Re: Ignite cache get operation not working, client application stucks at the initializaiton

Priyanka You need to provide reproducer as a project or at least all logs and thread dumps from all nodes, so somebody can help you. Evgenii 2018-03-30 15:08 GMT+03:00 Priyanka Shinde : > Hi, > Following is one of my cache configurations (we have same configuration

Re: Ignite cache get operation not working, client application stucks at the initializaiton

Hi, Following is one of my cache configurations (we have same configuration for all 3 caches) CacheConfiguration queueGrpcfg= new CacheConfiguration<>("queueGrpCache"); queueGrpcfg.setCacheMode(CacheMode.REPLICATED);

RE: How to insert multiple rows/data into Cache once

Hi Andrey, I am trying to run [2], as: // Register JDBC driver. Class.forName("org.apache.ignite.IgniteJdbcDriver"); // Opening connection in the streaming mode. Connection conn = DriverManager.getConnection("jdbc:ignite:cfg://streaming=true@file:///etc/config/ignite-jdbc.xml"); However, I'm a

Re: Error: class org.apache.ignite.IgniteException: Ignite instance with this name has already been started: igniteDual

>datastreamer which has all the configurations/properties per client basis. what do you mean? Why do you think so? It's definitely wrong to create a new client per thread, it creates a huge needless overhead. Evgenii 2018-03-29 8:28 GMT+03:00 Naveen : > The reason I

Hi is ignite have a plan for materialized view

Hi I wanna to use ignite like stream database。 I wanna to insert some logs like sale log。 and then ignite can let me create a materialized view to auto upate the count number or sum num number 。 I insert a salelog ：(time,vmcode,product)value('2018-03-30 14:00:00','21321','2123') a