JDBC thin client incorrect security context

Hi , We have built a security and audit plugin for security of our ignite cluster. We are unable to get the right audit information i.e. we are unable to get the right subject for users logged in through dbeaver ( jdbc thin client. ). This is because the subjectid associated with the "CACHE_PUT"

Re: JDBC thin client incorrect security context

HI Andrei, That helps..For some reason, i got confused and thought I am getting the UUID of the node on which it is running. thanks, regards, Veena. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: JDBC thin client incorrect security context

1. Another thing I noticed is that during a update through jdbc client, there could be 2 kinds of threads acting on it. The 'client-connector' thread and the 'sys-stripe'. If the client-connector thread completes the transaction and calls the record on storagemanager, it is able to send a

Transaction Ids associated with Cache Put (Atomicity mode TRANSACTIONAL)

I am also noticing when I do insert from the dbeaver( jdbc thin client ) the transaction id associated with the TX_STARTED/TX_COMMITTED event is different from the xid parameter sent with the Cache_PUT event . Why is this so ? Should the both not be the same ? -- Sent from:

Re: JDBC thin client incorrect security context

As suggested by you , i have put up this question on the 'ignite developers' forum as well. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: JDBC thin client incorrect security context

Hi Andrei, I checked again, The uuid associated with the cacheevent is associated to the node that handles the request from the jdbc thin client. It doesnt show the uuid of the logged in jdbc client(DBEAVER user). Do I need to do something to associate the cacheevent with the logged in jdbc

Regarding TRANSACTIONAL_SNAPSHOT

Hi, 1. We wanted to try TRANSACTIONAL_SNAPSHOT Atomicity Mode. Wanted to know if it is production version ?Asking since I noticed the below in the documentation . Not sure if this applies for the TRANSACTIONAL_SNAPSHOT atomicity mode as well .

Re: 2.8.0 : JDBC Thin Client : Unable to load the tables via DBeaver

This fails when the security plugin is enabled. When I remove the security plugin, the query goes through. With the security plugin enabled, it hangs at : GridReduceQueryExecutor - on awaitallReplies method. Attached screenshot of thread , when it hangs. Steps I take : 1. Start my server with

Re: 2.8.0 : JDBC Thin Client : Unable to load the tables via DBeaver

Hi , Yes, I have put 2.8.0 ignite core jar in the path for the DBeaver to pickup the latest jdbc jars. Steps to reproduce : 1. Create a table on dbeaver : CREATE TABLE TEST ( USERNAME VARCHAR, APPLICATIONNAME VARCHAR, MACHINENAME VARCHAR, PRIMARY KEY ( USERNAME)

Re: 2.8.0 : JDBC Thin Client : Unable to load the tables via DBeaver

index.jar is already in classpath of server. I added it on the dbeaver classpath ( Not sure, I dont think it is needed. ) I am on DBeaver 6.1.3. Here is what I do : 1. Clear my data directory. 2. Start the 3 servers with 2.8.0 3. Activate the cluster 4. Add the table via dbeaver : CREATE

Re: Local node terminated after segmentation

Thanks Evgenii -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Regarding EVT_NODE_SEGMENTED event

Hi , 1. Do we always get EVT_NODE_SEGMENTED event whenever after a node gets SEGMENTED ? I see the below in the javadocs for SegmentationPolicy : https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/plugin/segmentation/SegmentationPolicy.html *STOP* public static final

Re: PluginProvider method contracts

Hi Alex, Thank you for the reply . I guess I was looking for this >> the createComponent API is called internally by Ignite to create components inside your plugin So if your plugin has only one component, you can as well implement the createComponent and return the right processor. The

PluginProvider method contracts

Hi , I am having a look at the plugin provider to write a plugin. I am confused between these two methods : T plugin(); @Nullable T createComponent(PluginContext var1, Class var2); 1. What is the difference between the class returned by each of the method ? Are they both

Re: Local node terminated after segmentation

Hi Ilya, How can a node reachability resolver or Tcp Segmentation resolver help in discovering segmentation due to GC pauses ? What is the best way to discover segmentation on a node due to GC pauses ? regards, Veena -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Ignite Node failure - Node out of topology (SEGMENTED)

Hi Dmitry, Would having a segmentation plugin help to resolve segmentation due to GC pauses ? Or is the best resolution for long GC pauses is to resolve it and get the GC pauses to be within the failure detection timeout ? regards, Veena. -- Sent from:

Re: Regarding EVT_NODE_SEGMENTED event

>>It will help you when you have actual network issues and you 2 nodes are not able to communicate for some time, then Segment processor and resolver will help you* generate this event*. I guess even for network issues, when the node is marked as failed by the other nodes and it tries to join

Re: Regarding EVT_NODE_SEGMENTED event

Thanks Monal, What is the best way to generate a EVT_NODE_SEGMENTED event on the client side for testing the event handler ? ( I am able to generate this on server side. ) regards, Veena. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Regarding EVT_NODE_SEGMENTED event

Thanks for the reply Monal, >>Segment processor and resolver help you there. They help in what way ? The event generation itself doesn't need it . -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Regarding EVT_NODE_SEGMENTED event

I guess we always do receive a EVT_NODE_SEGMENTED event ( if we configure to receive it ) If we anyway receive EVT_NODE_SEGMENTED whenever the node gets segmented, ( i.e. whenever it tries to rejoin after the failureDetectionTimeout ), what is the use of the resolver checks ? -- Sent from:

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

Do you have security enabled in your project ? I think sqls not being able to run on dbeaver is a known issue on 2.8.0 for security enabled projects : https://issues.apache.org/jira/browse/IGNITE-12833 -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: 2.8.0 : JDBC Thin Client : Unable to load the tables via DBeaver

HI Ilya, Thank you for the invite. I will be very happy to debug and develop for Ignite. For the issue mentioned, I will debug a bit more and then file a ticket, regards, Veena. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Regarding EVT_NODE_SEGMENTED event

Thanks Ilya, Let me try. regards Veena. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

REPLICATED CACHE ISSUES WHEN UPDATED THROUGH JDBC THIN CLIENT - 2.7.6

HI, I am running a 3 server node cluster on Ignite 2.7.6 . 1. I have started a cache ( REPLICATED ) with native persistence enabled with the below configuration . cacheConfiguration.setRebalanceMode(CacheRebalanceMode.SYNC);

Re: Ignite Node failure - Node out of topology (SEGMENTED)

Hi Evgenii, Thank you for the reply and suggestion. regards, Veena. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Incorrect Value Received in Local Listener of Continuous Query when a 1000 row insert is triggered

We have about 5 clients. Each client starts 2 different CQ to the same cache abc . (We need 2 CQ since we want different action and different lifecycle when the local listener is triggered for either query. ) Client 1 : Say CQ1 is listening to changes to a record where name is name1. (There is a

Re: REPLICATED CACHE ISSUES WHEN UPDATED THROUGH JDBC THIN CLIENT - 2.7.6

Thanks Ilya, I will update the post with details a bit later. Stuck on another issue on ignite right now.( Will send a separate post ) -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Event for an update that should have been filtered is received in Local Listener of Continuous Query when a 1000 row insert is triggered

HI Alex, I am not able to reproduce this issue - we have seen it happening a few times in our test env. though. I am trying to go through logs and code to understand how it can happen. It looks like all the local listeners for this cache( about 6 of them ) have received the 'untransformed'

Re: Event for an update that should have been filtered is received in Local Listener of Continuous Query when a 1000 row insert is triggered

Hi Alex, Thank you for the reply . >> verify the continuous query definitions using the appropriate view: https://apacheignite.readme.io/docs/continuous_queries We are on 2.7.6 version. I guess this view is not available for us. Also we have been running the CQs for couple of months now in

Re: Event for an update that should have been filtered is received in Local Listener of Continuous Query when a 1000 row insert is triggered

I see this line being printed just before any local listener is invoked : 2020-05-06T16:28:17,909 INFO o.a.i.s.c.t.TcpCommunicationSpi [grid-nio-worker-tcp-comm-4-#255%ActivDataPublisher-ACTIVEI2-igniteclient-GREEN%]: Accepted incoming communication connection [locAddr=/x.x.x.x:yyy,

Re: 2.8.0 : JDBC Thin Client : Unable to load the tables via DBeaver

Hi , On further debugging, I found out that when security is enabled, and I do updates/selects from dbeaver, the security context in ctx.security().securityContext() in the class GridIOManager , method : createGridIoMessage returns me the securitycontext of the thin client. The message generated

Re: 2.8.0 : JDBC Thin Client : Unable to load the tables via DBeaver

HI , I created a ticket for Select Operation since IGNITE-12579 mentions only insert operation failure : https://issues.apache.org/jira/browse/IGNITE-12833 regards, Veena. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Server Node comes down when a node comes down and an update is issued within the failuredetectiontimeout

We have a 3 node server cluster ( Issue observed in 2.7.6, could not test in 2.8.0 because I am unable to bring up the dbeaver in 2.8.0 with securityplugin enabled )(http://apache-ignite-users.70518.x6.nabble.com/2-8-0-JDBC-Thin-Client-Unable-to-load-the-tables-via-DBeaver-td31681.html) A 4th

Re: 2.8.1 : EVT_NODE_RECONNECTED, EVT_NODE_SEGMENTED on the client side

Hi , Kindly awaiting a reply on this , regards, Veena -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite thread pool configuration

Thanks Denis, regards, Veena. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

IgniteSpiOperationTimeoutException: Operation timed out [timeoutStrategy= ExponentialBackoffTimeoutStrategy

Hi , Our setup : Servers - 3 node cluster Reader clients : wait for an update on an entry of a cache ( around 20 of them ) Writer Client : 1 If one of the reader client restarts while the writer is writing into the entry of the cache , the server attempts to send the update to the failed

Re: Lag before records are visible after transaction commit

Hi , >>Continuous Query itself is not transactional and it looks like it can't be used for this at the moment. So, it gets notification before other entries were committed. Does this mean we could get dirty reads as updates in continuous query ? i.e. for eg if the code is as below: 1. Start

Continuous query not transactional ?

Hi , This is in continuation of the below statement on this post : http://apache-ignite-users.70518.x6.nabble.com/Lag-before-records-are-visible-after-transaction-commit-tp33787p33861.html >>Continuous Query itself is not transactional and it looks like it can't be used for this at the moment.

Re: Ignite thread pool configuration

Thanks Denis, I am thinking of setting the below thread pools as this on both client and server since we dont use data streamer, IGFS or Peer Class loading: Also our thick clients dont connect using REST . So thinking of adding the below configuration on our thick

Re: 2.8.1 : EVT_NODE_RECONNECTED, EVT_NODE_SEGMENTED on the client side

Hi Team, In terms of the client, do we need to have the below 2 EVENT handlers? : 1. EVT_NODE_SEGMENTED - to restart the node and deploy and continuous queries if needed. 2. EVT_CLIENT_NODE_RECONNECTED - to just deploy the continuous queries ( no restart of ignite needed, since the node is

Re: IgniteSpiOperationTimeoutException: Operation timed out [timeoutStrategy= ExponentialBackoffTimeoutStrategy

Hi Team, Kindly awaiting a reply on this one, regards, Veena. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: 2.8.1 : EVT_NODE_RECONNECTED, EVT_NODE_SEGMENTED on the client side

Thanks Ilya, >>I don't think so. Node can reconnect to a *different* cluster, or it may be disconnected for a while and return to the same cluster. For client node, segmented/disconnected difference is not relevant. Neither it is for server node, in fact. In that case, we will have the same

Re: 2.8.1 : EVT_NODE_RECONNECTED, EVT_NODE_SEGMENTED on the client side

Thanks Ilya, >>I don't think so. Node can reconnect to a *different* cluster, or it may be disconnected for a while and return to the same cluster. For client node, segmented/disconnected difference is not relevant. Neither it is for server node, in fact. In that case, we will have the same

Re: Continuous query not transactional ?

Hi Ilya, That is what I assume too, could someone from the developers community help confirm/comment on this ? regards, Veena. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: 2.8.1 : EVT_NODE_RECONNECTED, EVT_NODE_SEGMENTED on the client side

Hi Anton, Thank you for the reply . >>I can confirm that there is no SEGMENTED event thrown on 2.8.1. I guess you meant that there is no SEGMENTED event thrown in 2.8.1 client when the servers are brought down and started again. Because SEGMENTED event could be thrown in 2.8.1 in other

Re: 2.8.1 : EVT_NODE_RECONNECTED, EVT_NODE_SEGMENTED on the client side

Hi Anton, Thank you for the reply . >>I can confirm that there is no SEGMENTED event thrown on 2.8.1. I guess you meant that there is no SEGMENTED event thrown in 2.8.1 client when the servers are brought down and started again. Because SEGMENTED event could be thrown in 2.8.1 in other

Re: 2.8.1 : Server cluster node startup issue

Thanks Alex, Will try and see if I can create a reproducer. >>If Ignite hasn't fully started, it will wait( U.awaitQuiet(startLatch); ) until it has, before returning the instance. Does the Ignition.start wait for the storage spi to return from record, to start ? since the storage spi is waiting

2.8.1 : Server cluster node startup issue

Hello, Our set up : Server nodes : 3 Writer application : 1 A event storage spi that writes the cache_put events that have been generated due to a dbeaver update into a ignite cache. We restarted one of the servers yesterday during regular business hours and noticed that the server was not

Re: 2.8.1 : Server cluster node startup issue

Hi Alex, 1. How is the storage spi record method getting invoked on this node if the ignite has not even fully started on this node ? Which ignite instance is it using to invoke the record method ? I have enabled only these events :

Re: 2.8.1 : INFO org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi [] - Accepted incoming communication connection

HI Anton, The setup I am working on is as below : server nodes : 3 client : 1 I get these logs when I start the client node within 10 secs of stopping it. There is no clue on the server nodes as to why these logs are printed. It looks as if the client node that was killed, is trying to join

Re: 2.8.1 : EVT_NODE_RECONNECTED, EVT_NODE_SEGMENTED on the client side

Hi Team, Kindly awaiting a reply on this, regards, Veena. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Webinar: Apache Ignite Management & Monitoring

Hi , I am trying to configure cluster in my machine with the control center agent to understand it. The servers are started using java so I tried to add the maven dependency or add the library as a external dependency to the project as mentioned in these slides

2.8.1 : MutableEntry.getValue().toBuilder throws NullPointerException

Hello, In some rare scenarios , we get this exception when we update records . java.lang.NullPointerException: null at org.apache.ignite.internal.binary.builder.BinaryBuilderReader.(BinaryBuilderReader.java:72) ~[ignite-core-2.8.1.jar:2.8.1] at

Re: 2.8.1 : MutableEntry.getValue().toBuilder throws NullPointerException

I have observed it on a subset of caches . We do not have assertions enabled. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: 2.8.1 : EVT_NODE_RECONNECTED, EVT_NODE_SEGMENTED on the client side

I rechecked this. My cluster setup is : servers : 3 client : 1 Bring down all nodes in the cluster for about 2 mins ( failuredetectiontimeout is 10 seconds ). The client receives EVT_NODE_RECONNECTED and does not receive EVT_NODE_SEGMENTED. -- Sent from:

Re: Ignite thread pool configuration

I noticed that the DataStreamer thread pool size seems to be around 32 in my local machine. In our cluster setup we dont stream data from any external db . We use native persistence. Do you think it makes sense to reduce this pool size for both server and client configuraiton. I am not sure if

Re: IgniteSpiOperationTimeoutException: Operation timed out [timeoutStrategy= ExponentialBackoffTimeoutStrategy

Hi Ilya, The node communication issue is because one of the node is being restarted - and not due to network failure . The original issue is as below : Our setup : Servers - 3 node cluster Reader clients : wait for an update on an entry of a cache ( around 20 of them ) Writer Client : 1 If

Re: IgniteSpiOperationTimeoutException: Operation timed out [timeoutStrategy= ExponentialBackoffTimeoutStrategy

Hi Ilya, The node communication issue is because one of the node is being restarted - and not due to network failure . The original issue is as below : Our setup :Servers - 3 node clusterReader clients : wait for an update on an entry of a cache ( around 20 ofthem )Writer Client : 1If one of the

Re: Event for an update that should have been filtered is received in Local Listener of Continuous Query when a 1000 row insert is triggered

Hello, Looks like this issue is not related to load, but related to remote filter not getting redeployed when a server node is restarted on version 2.7.6. Related discussion at http://apache-ignite-users.70518.x6.nabble.com/Remote-Filter-Execution-td33274.html regards, Veena. -- Sent

Re: Remote Filter Execution

I can also confirm that both these issues happen consistently on 2.7.6. All the nodes are in baseline when both these issues happen. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: 2.8.1 - Loading Plugin Provider

Hi Alex, Thanks for the reply, 1. I noticed that the ml plugin uses getPluginConfigurations which seems to have been deprecated.. https://github.com/apache/ignite/blob/master/modules/ml/src/main/java/org/apache/ignite/ml/util/plugin/MLPluginProvider.java Would that mean that the preferred way

2.8.1 : Ignite Security : Cache_Put event generated from a remote_client user action has subject uuid of Node that executes the request

Hi Team, 1. I noticed that this issue ( https://issues.apache.org/jira/browse/IGNITE-12781) is not resolved in 2.8.1. Could you guide how can we get audit information if a cache record modification is done on dbeaver and the cache_put event contains the node id instead of the remote_client

Re: 2.8.1 - Loading Plugin Provider - Conflicting documentation

Okay. If I set pluginconfiguration using setPluginConfiguration, how do I get it in the plugins ? getPluginConfigurations is deprecated in 2.8.1. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: 2.8.1 : EVT_NODE_RECONNECTED, EVT_NODE_SEGMENTED on the client side

Hi Anton, There are a few thoughts on this : 1. I found this issue after I upgraded from 2.7.6 to 2.8.1 ( No timeout values etc has been changed in our application ). So for the same scenario and the same application configuration a. in 2.7.6 , the client receives a evt_node_segmented b. in

2.8.1 : EVT_NODE_RECONNECTED, EVT_NODE_SEGMENTED on the client side

Hello, When do EVT_NODE_SEGMENTED event get generated on the client side in 2.8.1 ? I noticed that in 2.7.6 , when all the servers are restarted and the client reconnects again with a new node id - it used to receive a EVT_NODE_SEGMENTED . In 2.8.1 it receives EVT_NODE_RECONNECTED. Kindly

Re: 2.8.1 - Loading Plugin Provider - Conflicting documentation

HI , Raised a Documentation Improvement jira : IGNITE-13356 Documentation Change needed: PluginProvider loading changed from 2.8.1 regards, Veena. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: 2.8.1 - Loading Plugin Provider - Conflicting documentation

Hi Ilya, I have used the new style. It will also mean that this document is no longer the best way to load the plugin provider: https://apacheignite.readme.io/docs/plugins And this might need a documentation update. regards, Veena. -- Sent from:

Remote Filter Execution

Hello, We have a 3 server cluster . The Caches on this cluster are configured as PARTITIONED, with 1 BACKUP. We also have a client executing a simple continuous query awaiting updates on record where NAME=AA. 1. When this record is updated, I see the remote filter being executed only on one

Re: Remote Filter Execution

HI Ilya, Please find the attached logs. You will notice that this log is only on server 1 - "projectname LISTENS: Entered Remote Filter ." You can also see that the filter has been created on all the three nodes. ( LOG : projectname LISTENS: Filter created ) server1RemoteFilterExecuted.txt

Re: Remote Filter Execution

HI Ilya, I will put together something and post it here. regards, Veena. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Remote Filter Execution

Hi Ilya, Please find the reproducer project with a readme.txt. I have put in comments on how to reproduce both the issues mentioned in my original mail. regards, Veena. RemoteFilterIssueProject.zip

Re: Remote Filter Execution

Hi Ilya, Yes, So filter gets created but not executed on more than one node. 'Entered Remote Filter' happens only on one node. 'Filter created' log is printed in the 'create()' method of the Factory. 'Entered Remote Filter' is printed in the evaluate method of the CacheEntryEventFilter. That

Re: Cache_Put event generated from a remote_client user action has subject uuid of Node that executes the request sometimes

Hi Andrei, Could you kindly help review the approach to get the remote client user when the update is triggered from dbeaver ( jdbc thin client ). As mentioned this was done as a workaround to tackle this issue : IGNITE-12781 ( Wasnt sure if you were confirming the approach itself in the

Received metrics from unknown node

Hi all, Yesterday we had some network issues and we observed the server log having messages like : 2020-06-07T21:46:35,368 DEBUG c.c.p.c.c.p.d.CustomTcpDiscoverySpi [tcp-disco-msg-worker-#2]: Received metrics from unknown node: 8baf933f-e2cc-43be-818c-de2fb1259194 Once we figured which client

Re: Cache_Put event generated from a remote_client user action has subject uuid of Node that executes the request sometimes

HI Andrei, >>IgniteCache can help to hold all the information about started transactions and users. >>Using EventStorageSpi is a good way to handle the events. Thank you . I wanted a review on the below approach : 1.If the cache_put event holds the subject id of the remoteclient, then fetch it

Re: Received metrics from unknown node

Thanks Ilya. No. Did not take a thread dump. Will do so if I observe this behaviour next time. Also how do I add monitoring for such nodes ? regards, eena. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Cache_Put event generated from a remote_client user action has subject uuid of Node that executes the request sometimes

Cache_Put event generated from a remote_client user action has subject uuid of Node that executes the request sometimes. The Jira IGNITE-12781 was created by me for this. Some related conversation on this could be found at (

Re: 2.8.1 - Loading Plugin Provider - Conflicting documentation

Thanks Alex, There seems to be two conflicting documentation on loading the plugin provider : 1. The first way as shown in this documentation https://apacheignite.readme.io/docs/plugins : uses the Java Service Loader to load the plugin provider . It loads the plugin configurations through the

Re: Remote Filter Execution

HI Ilya, Did you use the reproducer project ? The CACHE configuration is PARTITIONED with ONE BACKUP. So should the remote filter evaluate method run on all the 3 nodes ? I would expect the evaluate method to run only 2 nodes I have not tried 2.8.1 yet. Will try and let you know. regards,

Re: Remote Filter Execution

Hi Ilya, I can confirm that both issues do not occur in 2.8.1. ( The remote filter evaluate executes only on 2 nodes as expected ..) Also the remote filter gets deployed whenever there is a server restart. The other thing for me to check is if we can use 2.8.1 ( We had issues on 2.8.0 jdbc thin

Re: 2.8.1 - Loading Plugin Provider - Conflicting documentation

Okay. >> The recommended way is to use the service provider as detailed here: How do we pass configuration for the provider in this approach. regards, Veena. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

2.8.1 - Loading Plugin Provider

Hi , I saw that 'SetPluginConfiguration' in IgniteConfiguration has been deprecated in 2.8.1: ( IgniteConfiguration javadoc : https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/IgniteConfiguration.html ) *IgniteConfiguration

Re: 2.8.1 : EVT_NODE_RECONNECTED, EVT_NODE_SEGMENTED on the client side

HI Anton, Checked again -In 2.8.1 it receives the EVT_NODE_RECONNECTED with a new node id . It receives Eventtype 17 ( EVT_NODE_RECONNECTED ) and not Eventtype 14 ( EVT_NODE_SEGMENTED ) . Also it connects with a new node id. Please find the log with relevant parts highlighted. 2020-07-31

Re: Client stuck on startup

>>Try to use some realistic value such as 64. I think it hadnt worked earlier - I will try again. client-log.txt Please find the client log file attached. I am seeing 'invoking shutdown hook..' as an INFO in the startup

Client stuck on startup

HI , One of the clients on my windows box sometimes gets stuck up on startup . I see this in the thread dump of the client. a. Not sure what those locked synchronizers are "main" #1 prio=5 os_prio=0 tid=0x02c9c800 nid=0x4404 waiting on condition [0x02c8e000]

Re: Client stuck on startup

This client is a sync which syncs around 1 million records from our old db to ignite . When I start the application, it runs the initial sync and I need a higher striped pool. I think the client sees starvation in striped thread pool when I give a small thread pool. ( I dont have the logs for

Re: 2.8.1 : INFO org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi [] - Accepted incoming communication connection

This issue is also observed if two different clients exist on the same box. Steps to reproduce : 1. Both the clients are not running 2. Start the client1 3. Stop the client 1 and start client 2 . 4. The huge set of logs are visible on client 2 logs. regards, Veena. -- Sent from:

Explicit Communication / Discovery port configuration on the client side needed ?

Hi , 1. If we deploy more than one client on same machine - should we explicitly configure communication and discovery port for the client i.e. should we do the below : 2. The localPortRange for communicationport and discovery port is 100 . Why is this

Re: Client stuck on startup

Okay, thanks Ilya . After it gets this issue, the app doesnt startup till I restart my server nodes. Is there anyway I can ensure clean shutdown when I face issues like this ? It looks like some ignite state is not cleaned up . regards, Veena. -- Sent from:

Regarding long running transaction

Hi , I see this in my transaction log : 2020-12-10T07:32:59,525 WARN o.a.i.i.diagnostic [grid-timeout-worker-#1035%config-sync-GREEN-igniteclient-SINGLE%]: First 10 long running transactions [total=1] 2020-12-10T07:32:59,525 WARN o.a.i.i.diagnostic

Regarding partition map exchange triggers

Hi , I can see the triggers for PME initiation here : https://cwiki.apache.org/confluence/display/IGNITE/%28Partition+Map%29+Exchange+-+under+the+hood Triggers Events which causes exchange Topology events: Node Join (EVT_NODE_JOINED) - new node discovered and joined topology (exchange is

Regarding partition map exchange triggers

Hi , I can see the triggers for PME initiation here : https://cwiki.apache.org/confluence/display/IGNITE/%28Partition+Map%29+Exchange+-+under+the+hood Triggers Events which causes exchange Topology events: Node Join (EVT_NODE_JOINED) - new node discovered and joined topology (exchange is

Regarding Partition Map exchange Triggers

Hi , I can see the triggers for PME initiation here : https://cwiki.apache.org/confluence/display/IGNITE/%28Partition+Map%29+Exchange+-+under+the+hood Triggers Events which causes exchange Topology events: Node Join (EVT_NODE_JOINED) - new node discovered and joined topology (exchange is done

Re: Regarding Partition Map exchange Triggers

>>Looking at your stack traces it seems that the cache you accessed in the SQL query was stopped right before the new client node is joined. >>All topology events are processed one-by-one, so the initial blocking time was caused by cache stop PME rather than client node join. What is the

Re: Regarding Partition Map exchange Triggers

Hi Ilya, thank you ! regards, Veena -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Regarding Partition Map exchange Triggers

Hi , I can see the triggers for PME initiation here : https://cwiki.apache.org/confluence/display/IGNITE/%28Partition+Map%29+Exchange+-+under+the+hood Triggers Events which causes exchange Topology events: Node Join (EVT_NODE_JOINED) - new node discovered and joined topology (exchange is done

Re: Unable to free disk space after keys are removed in ignite 2.7.0

Thank you .. ! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Regarding Partition Map exchange Triggers

HI Pavel, Thank you for the reply. >>> *for the end user , is this invoked when we do ignite.getOrCreate( xx ) and ignite.cache(xx )* >>Yes. getOrCreateCache would create a cache if doesnt exist . I would guess this would have the effect of starting the cache if doesnt exist . And I think

Re: 2.8.1 : INFO org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi [] - Accepted incoming communication connection

Hi Ilya, This is easy to reproduce. Have a server node and a client node in a cluster. Stop and start the client immediately so that the start happens within the failure detection timeout ( 10 sec typically ). You will see these messages in the client log as it is starting up the second time.

Re: IgniteSpiOperationTimeoutException: Operation timed out [timeoutStrategy= ExponentialBackoffTimeoutStrategy

Thank you for the suggestions. I will try the timeout settings. It looks like the server has connected to the client on the new client id using the discovery SPI but it is trying to send the cache update to the old client id using the communication SPI. What impact does the IgniteAsyncCallback

  1   2   >