Re: Starvation in striped pool

Ilya. What is most mysterious to me is, I disabled reconnect of think client (clientReconnectDisabled=true). Still the server prints, the below, where the same thick client is making an immediate attempt to reconnect back to the cluster, while the previous connecting isn't still successful.

Re: Starvation in striped pool

Attached are the logs. In the server log, you will see the thick client continuously pinging server indefinitely...there is no recovery of the thick client. SO, the problem is, we can't even reboot the thick client in a production scenario, as it does even fail (meaning, the configured failure

Authenticating communication between nodes using Ignite.Net

We are new to Ignite.Net and trying to implement few security feature before deciding final implementation in product. We had implemented authentication on Ignite Server and when connecting Thin client it user user id and password and working as expected. We had noticed that if we spun off

Re: Node stopped.

So the error sais to set clientFailureDetectionTimeout=3 1- Do I put a higher value than 3? 2- Do I do it on the client or the server nodes or all nodes? 3- Also if a client is misbehaving why shutoff the server node? On Thu, 3 Oct 2019 at 21:02, John Smith wrote: > But if it's the

Re: Issue with adding nested index dynamically

My apologies for multiple replies. Please consider latest reply -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Issue with adding nested index dynamically

I have tested with adding QuerySqlFields as well, it is enabling to add dynamic field and indexes on nested objects but if I restart the client again it is not able to join the grid because it is not able to find this column. But with the fix and maintaining proper aliases we are able to add

Re: Issue with adding nested index dynamically

ignite_bug_share.zip I have tested by adding QuerySqlFields as well, with or with out it, it is working when I add it, but if I restart the client it is not able to identify nested columns as its alias is null or

Re: Issue with adding nested index dynamically

ignite_bug_share.zip I have tested by adding QuerySqlFields as well, with or with out it, it is working when I add it, but if I restart the client it is not able to identify nested columns as its alias is null or

Apache Ignite Change data capture functionality

As part of change data capture functionality can apache ignite be integrated with Striim which is a real-time data integration software. I read that the same functionality can be achieved by integrating with Oracle Golden gate. But I am curious to know whether CDC is available via Striim. Thanks,

Re: Gracefully shutting down the cluster nodes

Hello! What kind of task are you talking about? Ignite has failover, so usually task will be transparently transferred to other node. To be extra sure you can call Ignition.stop(false) to make sure no current tasks are interrupted. Regards, -- Ilya Kasnacheev вт, 8 окт. 2019 г. в 20:49,

Cluster went down after "Unable to await partitions release latch within timeout" WARN

Hi There Igniters, We had a very strange cluster behivour while creating new caches on the fly. Just after caches are created we start get following warnings from all cluster nodes, including coordinator node; [2019-09-27T15:00:17,727][WARN

Re: Confusion with Events

Ivan, thanks for all of the help! I think we have it working based on your advice. I cannot seem to really reproduce it without following a very specific scenario outside of a test case. The test case works correctly - one change that I made was to change the predicate from looking for nodes

Re: Issue with adding nested index dynamically

Hello! Frankly speaking, I don't think this is a scenario that we want to support. If you are interested, you may like to start a discussion in dev@ list, but: working with nested objects is not a priority, and implicit configuration of a corner case is discouraged. In this case we recommend

Unresponsive cluster after "Checkpoint read lock acquisition has been timed out" Error

Hi There, We had a unresponsive cluster today after the following error; [2019-10-09T07:08:13,623][ERROR][sys-stripe-94-#95][GridCacheDatabaseSharedManager] Checkpoint read lock acquisition has been timed out.

Re: LifeCycleBean problem/question

Hi! I figured it out, when I test I use CTRL+C to stop the node and that makes the log4j2 builtin shutdown hook to execute and it looks it is executed in parallel with the jvm shutdown hooks and before Ignite is finished with shutdown, so I disabled log4j2's shutdown hook

Re: Partition loss due to node segmentation

Looks like I have not asked the correct question. Let me correct my question. If the cluster is segmented and 2 or more nodes out of total 5 nodes are thrown out of cluster then the data is lost (back up is set to 1). Now my question is does ignite fire the event

Re: LifeCycleBean problem/question

Hello! I don't think this should happen? Can you add breakpoint to this method (LogManager.shutdown), share stack trace with us once it gets hit? Regards, -- Ilya Kasnacheev вт, 8 окт. 2019 г. в 23:44, Mikael : > Hi! > > I gave up on the JUL logging so I went back to log4j 2, this works >

Re: Starvation in striped pool

Hello! It's hard to say what happens here. What timeout settings do you have? Can you provide complete log from client node as well? Regards, -- Ilya Kasnacheev вт, 8 окт. 2019 г. в 19:25, maheshkr76private : > Hello Ilya > Once connection goes bad between client and server, which

Re: Partition loss due to node segmentation

Hello Akash, Yes of course. As cluster is segmented, it is very well possible that cluster segment doesn't have all partitions in that segment. If you have backup partitions in the same segment, then only you have complete partitions. Best Regards, Gaurav On Wed, Oct 9, 2019 at 7:20 AM Akash