Re: Ignite 2.8.0. Heap mem issue

[akorensh]

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

   
  Attach Heap Dump as well, if you can. This will help us to diagnose the
issue faster.

heap dump:
https://www.gridgain.com/docs/latest/perf-troubleshooting-guide/troubleshooting#heap-dumps
to take dump of running process: jmap
-dump:live,format=b,file=/tmp/dump.hprof 12587

   
Thanks, Alex



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

Re: Ignite 2.8.0. Heap mem issue

[Evgenii Zhuravlev]

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 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
> node.
> The application consists of Apache Flume that inserts data into the cache
> and several Python scripts that read/write data from/into tables using SQL
> queries.
> Does anyone have experience with this behavior on Ignite 2.8.0. ?
> I tested using pyignite 0.3.4 and pygridgain 1.1.0.
> The same issue occurs on GridGain CE 8.7.12.
> On Ignite 2.7.5 with same application there is no issues with Heap mem.
> The screenshots below show that on Ignite 2.7.6 Heap Mem is always within
> normal ranges.
> One second screenshot Ignite 2.8.0. Heap mem only grows and application
> stops when the OOM happens. :-(
>
> JVM_OPTS
> -XX:+UseG1GC
> -XX:+AlwaysPreTouch
> -XX:+ScavengeBeforeFullGC
> -XX:+DisableExplicitGC
> -Xms512m -Xmx1g
>
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
> ^-- Node [id=1ce47741, name=UMBOSS, uptime=00:46:08.050]
> ^-- H/N/C [hosts=1, nodes=2, CPUs=8]
> ^-- CPU [cur=52.07%, avg=12.77%, GC=24.1%]
> ^-- PageMemory [pages=115217]
> ^-- Heap [used=1001MB, free=2.15%, comm=1024MB]
> ^-- Off-heap [used=455MB, free=80.61%, comm=1480MB]
> ^--   sysMemPlc region [used=0MB, free=99.99%, comm=100MB]
> ^--   metastoreMemPlc region [used=0MB, free=99.95%, comm=0MB]
> ^--   PersistDataRegion region [used=440MB, free=56.95%, comm=1024MB]
> ^--   TxLog region [used=0MB, free=100%, comm=100MB]
> ^--   DefaultDataRegion region [used=14MB, free=98.59%, comm=256MB]
> ^-- Ignite persistence [used=479MB]
> ^--   sysMemPlc region [used=0MB]
> ^--   metastoreMemPlc region [used=0MB]
> ^--   PersistDataRegion region [used=479MB]
> ^--   TxLog region [used=0MB]
> ^-- Outbound messages queue [size=0]
> ^-- Public thread pool [active=0, idle=0, qSize=0]
> ^-- System thread pool [active=1, idle=4, qSize=0]
>
>
>
> Best regards
>
> Dren
>
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t2557/Ignite_Heap_mem_issue.jpg>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Data Isolation during Ignite Cache load

[Evgenii Zhuravlev]

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 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 Name").loadCache(null).
>
> *Scenario:*
>
> We have built a rest service on top this cache and sends the data in the
> cache as response after applying some filters.Now During the time of Data
> load, if the user sends a get request and when we try to fetch the data
> from
> ignite cache will the filters be applied only the data that is loaded so
> far
> or does the filters be applied on the data that is available prior to the
> start of data load.
> *Please note we have set the Atomicity mode is set as Atomic for cache.*
>
>
> In case if  the filters are applied only on the data that is loaded so far,
> then is there a property that i need to set so that until the cache load is
> loaded , any query on the cache should fetch only the data that is
> available
> prior to the start of data load.Currently as per my observation,  i am able
> to see that the filters are applied only on the data that is loaded so far.
>
> Also can anyone help me the possible ways to schedule the Ignite cache
> refresh such that the ignite cache refresh job has to be triggered on the
> success condition of another unix shell script job.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: HOW TO CHANGE IGNITE JAVA THIN CLIENT PASSWORD

[dbutkovic]

 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

[DS]

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");
 Ignition.startClient(ClientCfg)

It throws an exception >
SEVERE: The user name or password is incorrect [userName=ignite]





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

Re: Query Entity and Affinity Key

[Evgenii Zhuravlev]

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 :

> Attached. thanks.
>
> On Mon, Mar 16, 2020 at 8:28 PM Evgenii Zhuravlev <
> e.zhuravlev...@gmail.com> wrote:
>
>> Hi, please share the whole config file
>>
>> пн, 16 мар. 2020 г. в 15:38, narges saleh :
>>
>>> Thanks Evgenii for the reply.
>>> How do I do that in XML configuration file if my query entities are
>>> defined solely in the xml file? What does ClassNameOfKey and
>>> fieldNameinThatClass represent? I assume I will have one bean for each
>>> cache.
>>> 
>>> 
>>> 
>>> 
>>> 
>>> >>
>>> value="fieldNameInThatClass"/>
>>> 
>>> 
>>> 
>>> 
>>> And the bean for the query entity is:have
>>>   
>>> >> value="java.lang.Integer"/>
>>> >> value="PERSON"/>
>>> >> value="PERSON"/>
>>> 
>>> 
>>> 
>>> >> value="java.lang.Integer"/>
>>>>> value="java.lang.Integer"/>
>>> >> value="java.lang.String"/>
>>> >> value="java.lang.String"/>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> CompanyId
>>> EmployeeId
>>> 
>>> 
>>> 
>>>
>>>
>>> On Mon, Mar 16, 2020 at 3:22 PM Evgenii Zhuravlev <
>>> e.zhuravlev...@gmail.com> wrote:
>>>
 Hi,

 You should have one cache per table(query entity) and configure
 separate CacheKeyConfigurations for each of the caches.

 Evgenii

 пн, 16 мар. 2020 г. в 11:42, narges saleh :

> Hi All,
>
> I have a question that might be trivial.
> If I define my query entity for each in the XML configuration file and
> define the affinity key via CacheKeyConfiguration (again in the xml file),
> considering that here affinity key is defined at IgniteConfiguration 
> level,
> how do I specify which cache keys (i.e., query entity key fields) will use
> the affinity key and which ones don't?
>
> Say I have these 4 tables
> Employee(company-id, employee-id)
> Contractor(company-id, contractor-id)
> Customer(company-id, customer-id)
> Company(company-id, address)
>
> How do I collocate employee, and contractors with companies but not
> the customers and companies? Can you provide the CacheKeyConfiguration and
> keyfields for each query entity?
>
> thanks.
>

Re: HOW TO CHANGE IGNITE JAVA THIN CLIENT PASSWORD

[Ilya Kasnacheev]

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?

[Ilya Kasnacheev]

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 not terminate the
> transactions. I would like understand more about the VM-level deadlock. How
> does one go about determining that?
>
> Thanks,
> rc
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Data Isolation during Ignite Cache load

[nithin91]

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 Name").loadCache(null).

*Scenario:*
 
We have built a rest service on top this cache and sends the data in the
cache as response after applying some filters.Now During the time of Data
load, if the user sends a get request and when we try to fetch the data from
ignite cache will the filters be applied only the data that is loaded so far
or does the filters be applied on the data that is available prior to the
start of data load.
*Please note we have set the Atomicity mode is set as Atomic for cache.*


In case if  the filters are applied only on the data that is loaded so far,
then is there a property that i need to set so that until the cache load is
loaded , any query on the cache should fetch only the data that is available
prior to the start of data load.Currently as per my observation,  i am able
to see that the filters are applied only on the data that is loaded so far.

Also can anyone help me the possible ways to schedule the Ignite cache
refresh such that the ignite cache refresh job has to be triggered on the
success condition of another unix shell script job.



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

Re: HOW TO CHANGE IGNITE JAVA THIN CLIENT PASSWORD

[dbutkovic]

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

[DS]

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 WITH
PASSWORD 'test'")).getAll()
}catch {...}

Using java thin client I am able to connect the server with default username
= 'ignite' and password = 'ignite'.

 if I try to change the password via above  Alter query, 
it throws me this error :

org.apache.ignite.internal.client.thin.ClientServerError: Ignite failed to
process request [1]: Operation failed
[nodeId=f0f0660d-3063-4a66-a25c-c8ca44d06cd2,
opId=c21a59ad071-98068f3f-df17-4b3e-9222-e747fc738ccf, err=class
org.apache.ignite.internal.processors.authentication.UserManagementException:
User doesn't exist [userName=IGNITE]] (server status code [1])










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

Ignite 2.8.0. Heap mem issue

[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 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
node.
The application consists of Apache Flume that inserts data into the cache
and several Python scripts that read/write data from/into tables using SQL
queries. 
Does anyone have experience with this behavior on Ignite 2.8.0. ? 
I tested using pyignite 0.3.4 and pygridgain 1.1.0. 
The same issue occurs on GridGain CE 8.7.12. 
On Ignite 2.7.5 with same application there is no issues with Heap mem. 
The screenshots below show that on Ignite 2.7.6 Heap Mem is always within
normal ranges.
One second screenshot Ignite 2.8.0. Heap mem only grows and application
stops when the OOM happens. :-(

JVM_OPTS
-XX:+UseG1GC
-XX:+AlwaysPreTouch
-XX:+ScavengeBeforeFullGC
-XX:+DisableExplicitGC 
-Xms512m -Xmx1g

Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=1ce47741, name=UMBOSS, uptime=00:46:08.050]
^-- H/N/C [hosts=1, nodes=2, CPUs=8]
^-- CPU [cur=52.07%, avg=12.77%, GC=24.1%]
^-- PageMemory [pages=115217]
^-- Heap [used=1001MB, free=2.15%, comm=1024MB]
^-- Off-heap [used=455MB, free=80.61%, comm=1480MB]
^--   sysMemPlc region [used=0MB, free=99.99%, comm=100MB]
^--   metastoreMemPlc region [used=0MB, free=99.95%, comm=0MB]
^--   PersistDataRegion region [used=440MB, free=56.95%, comm=1024MB]
^--   TxLog region [used=0MB, free=100%, comm=100MB]
^--   DefaultDataRegion region [used=14MB, free=98.59%, comm=256MB]
^-- Ignite persistence [used=479MB]
^--   sysMemPlc region [used=0MB]
^--   metastoreMemPlc region [used=0MB]
^--   PersistDataRegion region [used=479MB]
^--   TxLog region [used=0MB]
^-- Outbound messages queue [size=0]
^-- Public thread pool [active=0, idle=0, qSize=0]
^-- System thread pool [active=1, idle=4, qSize=0]



Best regards

Dren


 



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

Re: TcpDiscoverySpi worker thread failed with assertion error

[Ropugg]

Thanks, Mike! 
I will update and verify it.



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

Re: ClusterTopologyServerNotFoundException

[prudhvibiruda]

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 this error coming when we have only one node in our cluster?

Thanks for the quick reply,
Prudhvi



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

Re: Ignite client stuck

[mikle-a]

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: http://apache-ignite-users.70518.x6.nabble.com/