Thanks Anton & Mikhail for your responses.
I'll try to disable the WAL and test the cache preload performance. Also
will execute a JFR to capture some info.
@Mikhail I've checked the RDBMS perf metrics. I do not see any spike in the
CPU or memory usage. Is there anything in particular that could
Hi Bastien,
Ignore provides the ability to have distributed data structure. And in your
case an atomic long would work as a distributed counter.
For more info https://apacheignite.readme.io/docs/atomic-types
Regards,
Srikanta
On Wed, 26 Aug 2020, 12:24 pm Bastien Durel, wrote:
> Hello,
>
>
Currently I'm using Apache Ignite v2.8.1 to preload a cache from the RDBMS.
There are two tables with each 27M rows. The index is defined on a single
column of type String in 1st table and Integer in the 2nd table. Together
the total size of the two tables is around 120GB.
The preloading process
address them quickly:
> https://www.gridgain.com/docs/tutorials/spring/spring-ignite-tutorial
>
> -
> Denis
>
>
> On Fri, Aug 21, 2020 at 9:09 AM Srikanta Patanjali
> wrote:
>
>> I'm trying to integrate a Spring data project (without JPA) with Ignite
>
I'm trying to integrate a Spring data project (without JPA) with Ignite and
struggling to understand some basic traits. Would be very helpful if you
can share some insights on the issue I'm facing.
Currently the cache has been defined as below with the client node, this
config is not present in
Hi,
I'm using the "org.postgresql.ds.PGPoolingDataSource" dialect within the
datasource bean for Postgresql db.
The configuration of the datasource is independent of Ignite and can be
done as per the framework you are using.
Here is an example, if you are using Spring Boot -->
/wal WAL archive path: db/wal/archive
On Sun, Aug 16, 2020 at 4:11 PM Srikanta Patanjali
wrote:
> Found the below exception with further analysis of the logs :
>
> 2020-08-16 13:34:14,306 ERROR o.a.i.l.l.Log4J2Logger
> [jdbc-cache-loader-#10199%ig_svc_cluster%] Critical system er
exception being fixed recently as part
of https://issues.apache.org/jira/browse/IGNITE-10873
Are there any known reasons for the trigger of " Caused by:
java.lang.IllegalStateException: Duplicate row in index. " ?
On Sat, Aug 15, 2020 at 1:56 PM Srikanta Patanjali
wrote:
> Reshar
Resharing the cache settings as it got snipped in the previous email:
127.0.0.1:47500..47510
