Re: Ignite 2.8.0. Heap mem issue

Dren, Can you please attach the Flume/Ignite configs you are using and the relevant code. We will check this use case in 2.8.0. Please attach your server log/and GC logs GC logs info here: https://www.gridgain.com/docs/latest/perf-troubleshooting-guide/troubleshooting#detailed-gc-logs

Re: Ignite 2.8.0. Heap mem issue

Hi, Can you share configuration or even a code that you use? It would be nice to have a reproducer for this. Thanks, Evgenii вт, 17 мар. 2020 г. в 03:27, dbutkovic : > Hello, > I recently installed Ignite 2.8.0 on one node for test pourpose and noticed > Heap mem issue that I didn't have on

Re: Data Isolation during Ignite Cache load

Hi, > will the filters be applied What kind of filters? Do you mean SQL queries? Evgenii вт, 17 мар. 2020 г. в 07:47, nithin91 < nithinbharadwaj.govindar...@franklintempleton.com>: > Hi , > > We have Created a cache in Ignite that gets loaded with Data from > Oracle.Cache is getting loaded

Re: HOW TO CHANGE IGNITE JAVA THIN CLIENT PASSWORD

I think that username must be in single quote without \ igniteClient.query(new SqlFieldsQuery(" ALTER USER 'ignite' WITH PASSWORD 'password' ")); -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: HOW TO CHANGE IGNITE JAVA THIN CLIENT PASSWORD

Hello, The below query ran without throwing any error. : igniteClient.query(new SqlFieldsQuery("ALTER USER \"ignite\" WITH PASSWORD 'password'")); But when I am trying to connect with new password i.e. ClientCfg.setUserName("ignite"); ClientCfg.setUserPassword("password");

Re: Query Entity and Affinity Key

Hi, CacheKeyConfiguration can be defined on CacheConfiguration level: https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/CacheConfiguration.html#setKeyConfiguration-org.apache.ignite.cache.CacheKeyConfiguration...- пн, 16 мар. 2020 г. в 20:07, narges saleh : >

Re: HOW TO CHANGE IGNITE JAVA THIN CLIENT PASSWORD

Hello! ALTER USER "ignite" WITH PASSWORD 'new password'; Yep! Regards, -- Ilya Kasnacheev вт, 17 мар. 2020 г. в 15:00, dbutkovic : > try with ALTER USER 'ignite' WITH PASSWORD 'test' > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >

Re: How to terminate long running transactions in 2.4.0?

Hello! VM-level deadlock is a deadlock on synchronized blocks in Java. It's hard to say what happens in your case. Do you have a reproducer for this behavior? Regards, -- Ilya Kasnacheev пн, 16 мар. 2020 г. в 20:49, rc : > Hi Ilya, > > Thanks for responding. Killing the originator nodes did

Data Isolation during Ignite Cache load

Hi , We have Created a cache in Ignite that gets loaded with Data from Oracle.Cache is getting loaded using JDBC POJO Store method Ignite.Cache("Cache Name").loadCache(null).Can anyone explain how will ignite handle the below scenario when loading data using the method Ignite.Cache("Cache

Re: HOW TO CHANGE IGNITE JAVA THIN CLIENT PASSWORD

try with ALTER USER 'ignite' WITH PASSWORD 'test' -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

HOW TO CHANGE IGNITE JAVA THIN CLIENT PASSWORD

ClientConfiguration cfg = new ClientConfiguration() .setAddresses("127.0.0.1:10800") .setUserName("ignite") .setUserPassword("ignite"); try (IgniteClient igniteClient = Ignition.startClient(ClientCfg)) { igniteClient.query(new SqlFieldsQuery("ALTER USER IGNITE

Ignite 2.8.0. Heap mem issue

Hello, I recently installed Ignite 2.8.0 on one node for test pourpose and noticed Heap mem issue that I didn't have on 2.7.6. The Ignite configuration of dataStorageConfiguration / DataRegionConfiguration is identical. In production I have two nodes (2.7.6) and for test purpose (2.8.0) only one

Re: TcpDiscoverySpi worker thread failed with assertion error

Thanks, Mike! I will update and verify it. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: ClusterTopologyServerNotFoundException

Hi, We didn't explicitly define baseline topology. Because we don't want any of our nodes (all our nodes should be server nodes) waiting for other nodes. So at present with in our cluster we have only one server node. So you are saying that we should customize this baseline topology? But why is

Re: Ignite client stuck

Hi! Thanks a lot for your reply. I am absolutely sure that all ports are open and hosts are reachable because: 1) It had been working before 2) I was able to ping all other nodes from the client host while it was stucked 3) It started working after restart Any ideas? -- Sent from: