Best first steps for performance tuning

While looking at the docs, there are a lot of available parameters for performance tuning. We have several high-velocity Ignite operations, and Ignite is having trouble keeping up. We are using native persistence, and I suspect we will get more value from increasing the amount of memory used since

Don't miss my talk at the Apache Conference tomorrow!

In my talk at the Apache Conference tomorrow at 1:35 PM Mountain Time, I cover a few use cases where Ignite can be combined with Apache Pulsar for real-time use cases. Don't miss it! [image: image.png] https://www.apachecon.com/acah2020/tracks/pulsar.html Devin G. Bost

maxSize - per node or per cluster? - only 2k/sec in 11 node dedicated cluster

We're trying to figure out how to get more throughput from our Ignite cluster. We have 11 dedicated Ignite VM nodes, each with 32 GB of RAM. Yet, we're only writing at 2k/sec max, even when we parallelize the writes to Ignite. We're using native persistence, but it just seems way slower than expect

Re: maxSize - per node or per cluster? - only 2k/sec in 11 node dedicated cluster

gt; > [1] https://ignite.apache.org/docs/latest/persistence/persistence-tuning > [2] https://ignite.apache.org/docs/latest/data-streaming#data-streaming > Thanks, > Pavel > > пт, 13 нояб. 2020 г. в 07:26, Devin Bost : > >> We're trying to figure out how to get more

Split brain in 2.9.0?

We encountered a situation after a node unexpectedly went down and came back up. After it came back, none of our transactions were going through (due to rollbacks), and we started getting a lot of exceptions in the logs. (I've added the exceptions at the bottom of this message.) We were getting "Fa

Streaming Patterns and Best Practices - featuring Apache Ignite

I just released a new video that includes using Ignite in a couple of design patterns: Streaming Patterns and Best Practices with Apache Pulsar for Enabling Machine Learning and Analytics I thought it might be of interest to the community. Devin G. Bost

Ignite 2.8.1 - JMX scrape failed: java.lang.IllegalArgumentException

Hi, I noticed that we're getting a flood of these exceptions, and it looks like Ignite 2.8.1 claimed to fix the issue. However, we are running 2.8.1, and we're still seeing the issue. It looks to be the same issue that was discussed here: https://github.com/prometheus/jmx_exporter/issues/501 and

Re: unsubscribe

I'm not sure if you sent this to the right place. Did you get a confirmation email about being unsubscribed? Devin G. Bost On Thu, Feb 13, 2020 at 10:23 PM Shahid Muhamed < shahid.muha...@expeedsoftware.com> wrote: > unsubscribe > > Thanks, > > Muhamed Shahid >

Re: How to prevent Ignite downtime when adding tables & caches

We're using native persistence for each of them. Does dynamic cache creation work for tables? Is it possible to create tables dynamically that have persistence? Devin G. Bost On Wed, Feb 19, 2020 at 11:16 AM akurbanov wrote: > Hello, > > There is no need to restart the cluster if you want to c

Accessing cache from GridKernalContext?

Is there a way to access a cache (for performing Ignite lookups) from a GridKernalContext instance? Devin G. Bost

How to get client username in GridSecurityProcessor implementation

I'm trying to figure out how to obtain the client username from inside the GridSecurityProcessor's authorize method, but the only place where I can find the correct username is here: ((UserSecurityContextImpl) securityCtx).authContext.credentials().getLogin() The problem, however, is that authCon

SQL Error [08006]: Failed to communicate with Ignite cluster <-- BinaryObjectException: Not enough data to read the value

I created a plugin that implements GridSecurityProcessor because our implementation requries very specialized authorization; but now, whenever I try to run a SQL SELECT query on Ignite over JDBC, `AuthorizationProcessor.authenticate(..)` is run many times, like this: ``` Running AuthorizationPlugi

Re: SQL Error [08006]: Failed to communicate with Ignite cluster <-- BinaryObjectException: Not enough data to read the value

Hi Andrei, Thanks for the information. Do you know anything about when Ignite 2.8 will be released? It looks like the Maven packages are unavailable. Devin G. Bost On Tue, Mar 10, 2020 at 4:17 AM aealexsandrov wrote: > Hi, > > Can you please test the Apache Ignite 2.8. It should contain the f

Re: SQL Error [08006]: Failed to communicate with Ignite cluster <-- BinaryObjectException: Not enough data to read the value

ifacts in Maven: > https://search.maven.org/search?q=a:ignite-core > > Are you missing any particular package? > > - > Denis > > > On Tue, Mar 10, 2020 at 11:48 AM Devin Bost wrote: > >> Hi Andrei, >> >> Thanks for the information. Do you know anything

Re: SQL Error [08006]: Failed to communicate with Ignite cluster <-- BinaryObjectException: Not enough data to read the value

It turns out that I still get the SQL SELECT error even when using Ignite 2.8.0. Devin G. Bost On Tue, Mar 10, 2020 at 3:19 PM Devin Bost wrote: > Hi Denis, > > Thanks for the information! I think it was just my IntelliJ that was > complaining for no reason. I ran `mvn clean inst

Authenticate at cache-level

I'm working on an implementation of GridSecurityProcessor, which allows me to implement an authenticate method. However, all of the Ignite documentation I've found discusses creating users in SQL at the table-level. If I want authentication at the cache-level, do I need to create custom authenticat

Presentation - Real World Architectural Patterns with Apache Pulsar and Ignite

If anyone missed my presentation today on Real-World Architectural Patterns with Apache Pulsar that focuses on *Ignite* use cases and high-performance caching, you can access the recording here: https://youtu.be/pmaCG1SHAW8 Devin G. Bost