Re: same cache cannot update twice in one transaction

2019-02-26 Thread xmw45688
It seems that this enhancement has not been implemented yet for the following cases: trx.start() { 1. update t1 set col1='a' where col2='c'; 2. update the same table t1 with cache API. } trx.end(); Can someone confirm? many thanks, Xinmin -- Sent from:

Fwd: Re: On Multiple Endpoints Mode of JDBC Driver

2019-02-26 Thread 李玉珏
Hi, Since JDBC can't achieve multi-endpoint load balancing, we want to use affinityCall (...) mechanism to achieve load balancing, that is, to obtain and use JDBC Connection in IgniteCallable implementation. How to efficiently access and use JDBC Connection? 转发的消息 主题:

Re: Ignite Data streamer optimization

2019-02-26 Thread ashishb888
Sure. But in my case I can not do so. Any other options for single threads? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: web-console not displaying the latest version of ignite

2019-02-26 Thread Andrey Novikov
Hi, Looks like you are deployed old image of apacheignite/web-console-frontend. What version did you see in web-console footer? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite can not read the date type

2019-02-26 Thread gn01887818
Thank you. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Access a cache loaded by DataStreamer with SQL

2019-02-26 Thread Mike Needham
Hi All, I have a cache that I have loaded using the DataStreamer and can confirm there is a cache created by using the ignitevisor utility with the cache command. I cannot query it from any JDBC tools and am not sure why. Do I need to use a CREATE TABLE syntax in order for this to work instead

Re: Performance degradation in case of high volumes

2019-02-26 Thread Antonio Conforti
Hello, I recap the scenario of benchmark: 1) Constant submission of 4000 entries per second where every entry is an add (the key contains a field updatetime and changes for every entry). 2) The benchmark starts with no data in cache and the entries are submitted from an Ignite client node in

Re: OutOfMemoryError in ClusterProcessor.updateNodeMetrics

2019-02-26 Thread Ilya Kasnacheev
Hello! Unfortunaytely it seems that you will have to disable metrics for the duration. Regards, -- Ilya Kasnacheev вт, 19 февр. 2019 г. в 20:51, Ruslan Kamashev : > Probably it relates with > https://issues.apache.org/jira/browse/IGNITE-10925 > > On 18 Feb 2019, at 20:42, Ruslan Kamashev

introspection of ignite data

2019-02-26 Thread Scott Cote
I am trouble shooting a sql problem where I'm issuing a "select" statement and the parser is not finding my table . IgniteSqlException: Failed to parse query. Table "FOOBOO" not found; SQL statement:\nselect * from FOOBOO [42102-197] What API can I call against either an instance of

Re: Question about ignite data storage

2019-02-26 Thread Ilya Kasnacheev
Hello! 1) Roughly yes: you need to do checkpoint, RAM does not need wal/ but only db/, and also you need checkpoint page buffer with persistence which you can add to memory region when going pure-RAM. 2) I don't think that per cache metrics exist. Regards, -- Ilya Kasnacheev пн, 25 февр.

Re: Performance degradation in case of high volumes

2019-02-26 Thread Ilya Kasnacheev
Hello! Can you please provide full log? It's hard to say what is going on here. Can you please also share your Ignite/cache configuration and describe your work load? Regards, -- Ilya Kasnacheev пн, 25 февр. 2019 г. в 17:32, Dodong Juan : > I did observe the same thing with ignite and was

Re: Ignite can not read the date type

2019-02-26 Thread Ilya Kasnacheev
Hello! What do you expect to happen here? If it's a Date then use getDate(). Regards, -- Ilya Kasnacheev вт, 26 февр. 2019 г. в 12:52, gn01887818 : > Ignititedb defines a date type in a field. > JdbcResultSet uses the getBytes function (org.apache.ignite.internal.jdbc2) > Because the field

IgniteSpiException: Conflicts during configuration merge for cache

2019-02-26 Thread newigniter
I have two node cluster: each on its own separate machine. The replicated mode is turned on, as is native persistence. While inserting data to a cluster, one of the nodes failed(still checking why). When I want to bring it back up(or start a new one with the same configuration) it does not join

Ignite can not read the date type

2019-02-26 Thread gn01887818
Ignititedb defines a date type in a field. JdbcResultSet uses the getBytes function (org.apache.ignite.internal.jdbc2) Because the field will be java.sql.Date type, there will be an exception to the last else. How to deal with it? @Override public byte[] getBytes(int colIdx) throws SQLException

Re: C++ computer delay

2019-02-26 Thread Ilya Kasnacheev
Hello! Yes, this should do it. Maybe JVM is not started at the time of dump so only C++ threads are output? Can you dump C++ threads as well? (Since in this dump we only see top of stack as opposed to whole stack)?? Regards, -- Ilya Kasnacheev пн, 25 февр. 2019 г. в 16:20, F.D. : > Hi, > >