The code I'm using at the moment is here...
https://filebin.ca/5ihkjcOx8nid
Am 26.11.20 um 7:41 PM schrieb Wolfgang Meyerle:
Hi,
I'm now trying to connect to apache ignite via the odbc driver the whole
afternoon and now I'm stuck.
The compilation and the installation in the platform/cpp
Hi,
I'm now trying to connect to apache ignite via the odbc driver the whole
afternoon and now I'm stuck.
The compilation and the installation in the platform/cpp directory went
fine. Unixodbc driver was successfully installed according to the readmes.
I also double checked dependency
Hi did anyone have any possible suggestions for this? Thanks!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I had the same problem.
Maybe this can help.
http://apache-ignite-users.70518.x6.nabble.com/WAL-and-WAL-Archive-volume-size-recommendation-td34458.html
I disabled the wal archive and dimension the wal as 10 times wal segment
size (64 Mb by default, 256 in my case), and it works fine.
--
Hi,
It does not crash, it is just JVM uses system signals internally, you can
safely
ignore them or just ignore any signals coming from jvm.dll.
Best Regards,
Igor
On Thu, Nov 26, 2020 at 6:15 PM Ilya Kasnacheev
wrote:
> Hello!
>
> I think there should be some kind of guide on how to debug
Hi
I deployed 5 node Ignite 2.9.0 on k8s with below configuration
Total RAM per instance 64 GB
JVM 32 GB
Default data region 12 GB
Persistence storage 500GB volume
WAL + WAL archive 30 GB volume
After this I started ingesting data to 3 tables created, the data ingestion
is using basic JDBC batch
Hello!
I think there should be some kind of guide on how to debug JVM apps. I
would start with adding -Xint jvm arg to avoid JIT, which should make work
easier for both debugger and the VM.
Regards,
--
Ilya Kasnacheev
ср, 25 нояб. 2020 г. в 09:11, Wolfgang Meyerle <
