[Community] First Ignite Summit: May 25, 2021. How can you help

Hi, Igniters! It’s time to shine the spotlight on Apache Ignite—time for all of us to offer our knowledge and expertise to the broader developer community! On May 25, the first Ignite Summit will be held online: https://ignite-summit.org The idea is to share architectural best practices from Igni

Re: Insert with JDBC Thin driver into caches

Thanks. It fixes the issue. However, the javadoc for IgniteSystemProperties.IGNITE_BINARY_SORT_OBJECT_FIELDS says: @deprecated Should be removed in Apache Ignite 2.0. Is it ok to use it? Does it have any other impact? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite 2.9.1 - An existing connection was forcibly closed by the remote host

Hello! Have you gotten around collecting thread dump from the client? Regards, -- Ilya Kasnacheev вт, 16 февр. 2021 г. в 16:59, Charlin S : > Hello, > Thanks for your help, > I am not sure where to check the network misconfiguration either in System > or in Application configuration (ignite e

Re: (Ignite ver: 2.6)Failing client node due to not receiving metrics updates from client node

What does it say on the client side? If it’s a network issue, there are at least two parties and we can’t be sure what’s happen just by looking at one side. Sometimes it’s genuinely a network issue. Other times it’s a long JVM pause. Others it’s a bug, like the one you identified. Regards, Ste

Re: Insert with JDBC Thin driver into caches

It is marked as deprecated because there were plans to make it enabled by default. But it is still not... Now the property is already deprecated, but the feature is still disabled by default. -- Thanks вт, 16 февр. 2021 г. в 20:06, Benjamin : > Thanks. It fixes the issue. > > Howeve

Re: Ignite 2.9.1 - An existing connection was forcibly closed by the remote host

Hello, Thanks for your help, I am not sure where to check the network misconfiguration either in System or in Application configuration (ignite ean file). I am thinking to reduce interval to 1 min and retry count 5 and currently its 2 minutes and 10 times. My current configuration is as below and p

(Ignite ver: 2.6)Failing client node due to not receiving metrics updates from client node

I am using ignite 2.6 version. Ignite client node is failing in prod env giving following warning. So I changed the clientFailureDetectionTimeout to 9 millis. But this did not solve the problem. I am still facing this issue. 1) Can someone please explain the reason for this issue? Is it rea

Re: Insert with JDBC Thin driver into caches

But this property should be set on the empty cluster before you create your schema - Ilya вт, 16 февр. 2021 г. в 16:53, Ilya Kazakov : > Hello, Benjamin! > > Try to run your Ignite with system property: > -DIGNITE_BINARY_SORT_OBJECT_FIELDS=true > > Or from Java: > >

Re: Ignite 2.9.1 - An existing connection was forcibly closed by the remote host

Hello! It should be JVM thread dump. Packet drops is one thing, network misconfiguration is another. Regards, -- Ilya Kasnacheev пн, 15 февр. 2021 г. в 15:12, Charlin S : > Hello, > Thanks for your help, > As per our network team, there were no packet drops between client and > server. > Do

Re: [2.10 branch]cpp thin client transaction :Transaction with id 1 not found.

Hello! In fact, it's very simple: int main() { IgniteClientConfiguration cfg; cfg.SetEndPoints("10.250.0.10, 10.250.0.4"); try { IgniteClient client = IgniteClient::Start(cfg); CacheClient cache = client.GetOrCreateCache("vds"); ClientTransactions transacti

Re: Insert with JDBC Thin driver into caches

Hello, Benjamin! Try to run your Ignite with system property: -DIGNITE_BINARY_SORT_OBJECT_FIELDS=true Or from Java: public static void main(String[] args) throws SQLException { System.setProperty("IGNITE_BINARY_SORT_OBJECT_FIELDS", "true"); ... - Thanks,