Re: Remote Filter Execution

Hello! There's nothing we can do about 2.7.x right now, I suggest upgrading to 2.8.1. Regards, -- Ilya Kasnacheev пт, 17 июл. 2020 г. в 10:06, VeenaMithare : > I can also confirm that both these issues happen consistently on 2.7.6. All > the nodes are in baseline when both these issues

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: 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: 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

Hello! I have just checked this behavior on 2.8.1, and I don't see any of these issues popping up. All 3 server nodes run remote listener (judging by log), and after restarting of nodes I can still see updates on 'id1' appearing in client npde's log. I didn't check it on 2.7.6. Can you confirm

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, 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

Hello! Maybe there's something with your filter implementation which prevents it from functioning. Can you throw together a small reproducer project to show this behavior? Regards, -- Ilya Kasnacheev пт, 10 июл. 2020 г. в 19:35, VeenaMithare : > Hi Ilya, > > Yes, So filter gets created but

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: Remote Filter Execution

Hello! I see the following lines on all 3 nodes: 2020-07-09 16:41:02,957 [disco-notifier-worker-#101] DEBUG com.COMPANYNAME.prophet.configstore.common.remote.ConfigStoreTableRemoteFilterFactory [] - projectname LISTENS: Filter creation started with

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

Hello! This is weird, I recommend checking logs for exceptions, maybe the filter cannot run on two other server nodes. Regards, -- Ilya Kasnacheev пт, 10 июл. 2020 г. в 10:25, VeenaMithare : > Hello, > > We have a 3 server cluster . The Caches on this cluster are configured as >

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