How can I unsubscribe from the email server?

2018-10-16 Thread Lucky
There are too many emails . How can I unsubscribe from the email server? Thanks.

unsubscribe

2018-09-16 Thread Lucky
unsubscribe

Where is the data stored in Durable Memory?

2018-04-01 Thread Lucky
Hi Where is the data stored in Durable Memory? I want to find the data in hard disk. There is no description in the document. Thanks. Lucky.

Re:Re: Re: About Apache Ignite 2.4 with jdk

2018-03-19 Thread Lucky
Ignite server can use JDK8. But my system can not support JDK8. So I have to build a JDK7 version for client. Thanks. At 2018-03-19 19:27:24, "piyush" wrote: >If possible dont rebuild the source, just use JDK8 instead of JDK7. >According my observation in my project JDK8 performs lot better t

Re:Re: About Apache Ignite 2.4 with jdk

2018-03-19 Thread Lucky
I have downloaded the source. But ,there are some code use JDK 1.8, like this: 在 2018-03-19 16:41:06,"Nikolay Izhikov" 写道: >Hello, Lucky. > >You can download source of Ignite from official repository: > >https://ignite.apache.org/download.cgi#sources > > &g

About Apache Ignite 2.4 with jdk

2018-03-19 Thread Lucky
Hi, Apache Ignite 2.4 is built in JDK1.8. Can you provide a JDK1.7 version? Or Give the dependency jar list ,then I can build it myself. Thanks very much.

Re:Re:RE: Re: Node can not join cluster

2018-03-15 Thread Lucky
Well, I've solved this problem. Thanks a lot.

Re:RE: Re: Node can not join cluster

2018-03-15 Thread Lucky
Hi, I load data from database with 192.168.63.36 node. The other node don't load data. This you can see it from default-config_60.xml and default-config.xml file. I have provide files all about this . Thank you. At 2018-03-06 16:53:49, "Stanislav Lukyanov" wrote: Hi, As Ale

Re:Re: Node can not join cluster

2018-03-05 Thread Lucky
Hi It's been over a few months. Are there any suggestions? Thanks. At 2017-12-15 23:35:49, "afedotov" wrote: >Hi, > >From logs, I can see that the node was not able to connect to the cluster >due to a timeout issue. >It could be caused by GC or network issue. Please check the l

Re:Re:Re: Re:Re: delete data error

2018-01-22 Thread Lucky
09:38:18, "Lucky" wrote: I put the entry like this: cache.put(entry.getFID(),entry); The fid is a UUID, is only. I'm very sure that the data in the cache is no problem. All value is correct,and look like the other record. sql="delete from \"tmpCompanyCuBaseDataCach

Re:Re: Re:Re: delete data error

2018-01-22 Thread Lucky
anyCuBaseData" again, It got the same error, the key had changed to another one. And When I delete this record ,execute again ,it's the same.. Thanks. Lucky. At 2018-01-22 22:28:59, "Ilya Kasnacheev" wrote: Hello! Thank you for the log! It looks like there'

Re:Re:Re: delete data error

2018-01-21 Thread Lucky
Is there any suggestion? At 2018-01-18 09:56:51, "Lucky" wrote: This did not happen every time. When I run it several times,it will happen .And when it happened, then it will happened every time. This table is simple; I insert some data and when I finish the job,I will delet

Re:Re: delete data error

2018-01-17 Thread Lucky
te: >Hello Lucky! > >Does this happen every time when you try, or it is a one-time occurrence? > >Can you please share logs from your nodes and cache/table configurations? >Ideally a small reproducer project. > >Regards, > > > ignte.rar Description: Binary data

delete data error

2018-01-16 Thread Lucky
Hi When delete some data,it got an error. sql = "delete from \"tmpCompanyCuBaseDataCache\".TmpCompanyCuBaseData "; cache.query(new SqlFieldsQuery(sql)) I use jdbc to excute this sql ,it's the same. This table has about 20 records. I had check the data ,and found the data is

Re:Re: Node can not join cluster

2017-12-18 Thread Lucky
All the logs of nodes in Ignite cluster are the same.

Re:Re: Node can not join cluster

2017-12-18 Thread Lucky
Well,I run the ignite cluster in a physical machine with 2T ram. All virtual machines configuration are the same. And I have checked the port ,it's also normal . All of Ignite cluster node also are working properly. Thanks. At 2017-12-15 23:35:49, "afedotov" wrote: >Hi, > >From logs, I

Node can not join cluster

2017-12-13 Thread Lucky
connection [rmtAddr=/192.168.63.47, rmtPort=45884] [09:07:36,868][INFO][tcp-disco-sock-reader-#7][TcpDiscoverySpi] Started serving remote node connection [rmtAddr=/192.168.63.47:45884, rmtPort=45884] The attachment is one node of the cluster's trace. All the thing are as same as the ot

Re:Re: Re: Re: Re: Re: Re: Re: Re:Poor performance select query with jdbc thin mode

2017-12-11 Thread Lucky
Denis, Thanks very much! All data are related ,and there are about 60G data in the heap. And if I add other business module ,the data also are related.We can not split them. So If data is collocated, then a single node is enough. But it's not high availability.

Re:Re: Re: Re: Re: Re: Re: Re: Re:Poor performance select query with jdbc thin mode

2017-12-06 Thread Lucky
Denis, Thanks very much! All data are related ,and there are about 60G data in the heap. And if I add other business module ,the data also are related.We can not split them. So If data is collocated, then a single node is enough. But it's not high availability. At 2017-1

Re:Re: Re: Re: Re: Re: Re: Re: Re:Poor performance select query with jdbc thin mode

2017-12-06 Thread Lucky
well,3 node took about double time of single node.

Re:Re: Re: Re: Re: Re: Re: Re:Poor performance select query with jdbc thin mode

2017-12-06 Thread Lucky
explain : SELECT T0__Z0.FID AS __C0_0, T0__Z0.FCUSTOMERGROUPSTANDARDID AS __C0_1, T0__Z0.FCUSTOMERGROUPID AS __C0_2, T0__Z0.FCUSTOMERID AS __C0_3, T0__Z0.FCUSTOMERGROUPFULLNAME AS __C0_4 FROM "csspGroupStandardCache".CSSPGROUPSTANDARD T1__Z1 /* "csspGroupStandardCache".C

Re:Re: Re:Re: index about jdbc thin mode

2017-12-05 Thread Lucky
The code is here: String sql = "explain SELECT FID,FNUMBER FROM \"customerCache\".CustomerIgniteInfo WHERE FUSEDSTATUS = 3)"; Class.forName("org.apache.ignite.IgniteJdbcThinDriver"); Connection conn = DriverManager.getConnection("jdbc:ignite:thin://192.168.63.36?distributedJoins=true"); Pre

Re:Re: Re: Re: Re: Re: Re:Poor performance select query with jdbc thin mode

2017-12-05 Thread Lucky
No, the problem is poor performance. This query should not take that time. That just took 10ms in oracle ,but It took 2200ms in ignite. Thanks.

Re:Re: Re: Re: Re: Re:Poor performance select query with jdbc thin mode

2017-12-05 Thread Lucky
now it is about the same as JDBC thin mode. At 2017-12-05 16:52:48, "Denis Mekhanikov" wrote: Lucky, Thanks for the code. And what is the time for cache.query() for the same query? Denis

Re:Re: Re: Re: Re:Poor performance select query with jdbc thin mode

2017-12-05 Thread Lucky
cDriver execute sql2 time ="+(t1-t2)+"ms"); } catch (Exception e) { logger.error(e); } } the log is here: [(TestMain.java:417)]IgniteJdbcThinDriver getconn time =245ms [(TestMain.java:420)]IgniteJdbcThinDriver preparedStatement time =8ms resultSet==3NsAAABJbRloQTCA [(TestMain.java:425)

Re:Re: index about jdbc thin mode

2017-12-04 Thread Lucky
afedotov, As you say ,you removed JPA related annotations. How to removed? I try as your suggestion, I found if I build a new entity class and use cache.query() ,it will take the index, but still not take the index with JDBC thin mode. What did I miss? Thanks.

Re:Re: Re: Re:Poor performance select query with jdbc thin mode

2017-12-04 Thread Lucky
. And I change the join order some queries, it happened nothing. Thanks. 在 2017-12-01 23:52:48,"Denis Mekhanikov" 写道: Lucky, If you enable enforceJoinOrder option, then join operations will be performed in the exact order, in which they appear in the query. This flag p

Re:Re: index about jdbc thin mode

2017-12-04 Thread Lucky
well, I use jdbc thin mode. It's ok with cache.query(); But It did not work with JDBC thin mode. Thanks.

index about jdbc thin mode

2017-12-04 Thread Lucky
STATUS(Integer fUSEDSTATUS) { FUSEDSTATUS = fUSEDSTATUS; } } My ignite version is 2.3. Should this be a full table scan? It took more time. 1. I want to know why this happened. 2. How can I create a correct index? Thanks. Lucky

Re:Re: Re: Re: Re: JdbcQueryExecuteResult cast error

2017-11-30 Thread Lucky
Denis, Another thing, the JDBC connection can be closed automatically?

Re:Re: Re: Re: Re: JdbcQueryExecuteResult cast error

2017-11-30 Thread Lucky
Denis, add additional synchronization? But how? Thanks. At 2017-11-30 14:52:05, "Denis Mekhanikov" wrote: Lucky, If it's possible, that this code is executed cuncurrently, then you need to add additional synchronization. Otherwise correct work of JDB

Re:Re: Re:Poor performance select query with jdbc thin mode

2017-11-30 Thread Lucky
Denis, It's worse! There just have several sql can be faster, the other took more time. Thanks. 在 2017-11-29 21:31:05,"Denis Mekhanikov" 写道: Lucky, Try enabling enforceJoinOrder parameter in JDBC connection string and let us know the result. Your JDBC connectio

Re:Re: Re: Re: JdbcQueryExecuteResult cast error

2017-11-29 Thread Lucky
normal. Thank you very much. At 2017-11-29 18:37:33, "Denis Mekhanikov" wrote: Lucky, What tool are you using to access Ignite over JDBC? Does this problem reproduce, if you use DBeaver, for example? As Taras said, looks like the same JDBC connection is used concurrently. Denis

Re:Re:Poor performance select query with jdbc thin mode

2017-11-28 Thread Lucky
Have you come to a conclusion? At 2017-11-27 17:23:16, "Lucky" wrote: Hi,Denis: 2.3 will be better than 2.2. But the performance improvement is not obvious. It took 2.5 seconds in single ignite node ,and took 5 seconds in cluster(3 ignite nodes). JDBC Cli

Re:Re: Re: JdbcQueryExecuteResult cast error

2017-11-28 Thread Lucky
quot;Denis Mekhanikov" wrote: Lucky, Could you provide a full stack trace? It's hard to say, what happened, by the part, that you sent in the first message. Denis пн, 27 нояб. 2017 г. в 19:39, Lucky : Hi, Because our company's network do not allow send file to the inte

Re:Re: JdbcQueryExecuteResult cast error

2017-11-27 Thread Lucky
h all records with jdbc.it got the error . By the way, my server node and clent node are all use ignite-core.2.3.jar, ignite-index2.3.jar. Do I miss something? Thanks. Lucky At 2017-11-27 23:42:42, "Taras Ledkov" wrote: Hi, Another simple check: How ma

Re:Poor performance select query with jdbc thin mode

2017-11-27 Thread Lucky
Hi,Denis: 2.3 will be better than 2.2. But the performance improvement is not obvious. It took 2.5 seconds in single ignite node ,and took 5 seconds in cluster(3 ignite nodes). JDBC Client driver is worse than JDBC thin driver. it took about more 1 seconds. Did there a

JdbcQueryExecuteResult cast error

2017-11-25 Thread Lucky
Hi The ignite version is 2.3 When I update something by cache.query(new SQLFieldsQuery(sql)), and then I execute query to get new records with jdbc thin mode, It's got an error: Caused by: java.lang.ClassCastException: org.apache.ignite.internal.processors.odbc.jdbc.JdbcQueryExec

Re:Re: Re: Fetched result use too much time

2017-10-11 Thread Lucky
My ignite version is 2.2. 在 2017-10-10 20:58:55,"Andrey Mashenkov" 写道: Hi Lucky, Looks like your query selectivity is poor and even with GroupBy large amount of data shoud be fetched to reduce node. 1. Is it possiblt to coolocate data on field used in OrderBy clause? 2. L

Re:Re: Fetched result use too much time

2017-10-10 Thread Lucky
the record is too large, it need 4 hours to load data to ignite.So I have to wait. 3.Actually, if I remove the group by clause and having condition, it took more time! 4 and 5: I have try them before ,but it did not work. Thanks again. Lucky At 2017-09-21 21:28:40, "Andrey Mash

insert data took too much time

2017-10-10 Thread Lucky
Hi, I excute the sql like this: insert into "mycache".cacheInfo (_key,fid) values('111','111'),('222','222') ... This will insert 9 records at one time and it took 100 seconds. I create index on column fid. The ignite version is 2.2 and the table has no record. the conf

回复: Fetched result use too much time

2017-09-21 Thread Lucky
the record is too large, it need 4 hours to load data to ignite.So I have to wait. 3.Actually, if I remove the group by clause and having condition, it took more time! 4 and 5: I have try them before ,but it did not work. Thanks again. Lucky 在2017年09月21日 21:28,Andrey Mashenkov 写道

回复: Fetched result set too large

2017-09-19 Thread Lucky
I see. Thanks a lot! 2017年09月19日 13:49,slava.koptilin : Hi Lucky, You just need to start grid with -DIGNITE_SQL_MERGE_TABLE_MAX_SIZE=3 JVM flag. Thanks, Slava. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

回复: Fetched result set too large

2017-09-18 Thread Lucky
I see the document you refer to.but I don't know how to set this property value. I excepted to use java code . Is there any example? Thanks. Lucky 2017年09月18日 22:50,Вячеслав Коптилин : Hi Lucky, It seems that I was wrong. You need to increase the value of IgniteSystemPro

回复: Fetched result use too much time

2017-09-18 Thread Lucky
record in the in condition. That's the record we need. This is the business scenario required. I can't change this. Thanks for your suggestion. Lucky 2017年09月18日 21:55,Vladimir Ozerov : Hi Lucky, Could you please share you data model and node/cache configuration? I want to make

Re:Re: Re: Fetched result use too much time

2017-09-16 Thread Lucky
I do not understand your points exactlly. but I have post the screenshot here. It is the output of the "explain" query. Can you see that? At 2017-09-16 15:28:23, "Dmitriy Setrakyan" wrote: Lucky, We would like to see the output of the "EXPLAIN" command fo

Re:Re: Fetched result use too much time

2017-09-15 Thread Lucky
;).setArgs(newObject[]{newInteger[]{2,3,4}})) but it also need take 82 seconds.That did not change anything. Any other suggestion? Thanks a lot. Lucky At 2017-09-15 22:17:30, "Yakov Zhdanov" wrote: Please run explain from Ignite, not from H2 console - https://apacheignite.read

Re:Re: Re: Re: Fetched result set too large

2017-09-14 Thread Lucky
Yes,It work. Thank you. At 2017-09-14 00:26:07, "Alexey Kuznetsov" wrote: Hi Lucky, You can build Ignite from sources. Will this work for you? On Wed, Sep 13, 2017 at 9:07 PM, Lucky wrote: Oh,No! This is the worst news today. I have to try another way to resolve it. Any

Re:Re: Re: Fetched result set too large

2017-09-13 Thread Lucky
Oh,No! This is the worst news today. I have to try another way to resolve it. Anyway,Thanks a lot. At 2017-09-13 14:46:00, "Вячеслав Коптилин" wrote: Hi Lucky, Unfortunately, there is no release date on Apache Ignite releases page [1]. Usually, new Ignite release become avail

Re:Re: Fetched result set too large

2017-09-12 Thread Lucky
Thanks. When will the 2.3 be released? At 2017-09-12 22:58:34, "slava.koptilin" wrote: >Hi Lucky, > >It seems that this issue was resolved >https://issues.apache.org/jira/browse/IGNITE-5991 >The fix will be available in Apache Ignite 2.3 > >Thank

Fetched result set too large

2017-09-11 Thread Lucky
in(Ids) group by did having count(did)>=3000' return few records ,this sql is work,but if it return 20,000 records(actually it's often return 10 million records),it got this wrong message:Fetched result set war too large. And the whole sql is expected 30,000 records. Any suggestion? Thanks. Lucky.

Re:Re: many users used a temptable

2017-09-06 Thread Lucky
Ok,it is work. Thanks you very much. At 2017-09-07 01:43:12, "Mikhail" wrote: >Hi Lucky, > >Ignite supports DDL: > >https://apacheignite.readme.io/docs/distributed-ddl > >you can create and drop tables as much as you want. > >Thanks, >Mikhail. &g

many users used a temptable

2017-09-06 Thread Lucky
Hi I encountered such a problem: I have been loaded with some cache data in ignite, and then creates a temporary table and write data, and associate query with these cached data, delete the temporary table after use; support such a scene in ignite?

Re:Re: ignit2.1 start h2 debug console error

2017-09-06 Thread Lucky
Thanks a lot! It's work! At 2017-09-04 17:15:35, "ilya.kasnacheev" wrote: >Hello Lucky, > >It should be -DIGNITE_H2_DEBUG_CONSOLE=true > >note the "D" after dash, that means "define property" >and the absense of whitespace before equals

ignit2.1 start h2 debug console error

2017-09-03 Thread Lucky
Hi I can not start h2 debug console . ignite version: 2.1 os: centos6 when I start it by ./ignite.sh , this is the error message:

Re:Re: Re:Re: about write behind problems

2017-07-20 Thread Lucky
Of cource I did. cacheCfg.setWriteThrough(true); At 2017-07-21 10:38:00, "vkulichenko" wrote: >Did you set the writeThrough property? It's needed to enable write to cache >store, regardless of whether it's write-behind mode or not. > >cacheCfg.setWriteThrough(true); > >-Val > > > >-- >View

Re:Re: about write behind problems

2017-07-20 Thread Lucky
dBatchSize is set to 1 and setWriteBehindFlushFrequency is set to 5 seconds,but in the log ,I see that is not 1 each time,and There is no interval of 10 seconds Thanks. Lucky At 2017-07-21 03:18:06, "vkulichenko" wrote: >Hi Lucky, > >Write behind affects the way how under

write behind problems

2017-07-19 Thread Lucky
eCycleBean(after_node_start event) to load above configure and load all datas to cache. Any suggestion? Thanks. Lucky

Re:Re: Requested array size exceeds VM limit

2017-07-16 Thread Lucky
Thanks all. I know how to do it . Lucky At 2017-07-15 21:45:06, "Denis Magda" wrote: Starting Ignite 2.0 data is always in off-heap meaning you can easily store and process terabytes of data in the cluster. Java heap is needed only for operational needs of your applicati

Re:Re: Re: Requested array size exceeds VM limit

2017-07-15 Thread Lucky
OK .I see. But My data is more than 80GB, and it will rise to 120G the next 3 years, and I want to let my data always resides in off heap. My ignite version is 2.0. Any suggestion? Thanks. Lucky At 2017-07-14 21:27:21, "Andrey Mashenkov" wrote: Hi Lucky, It is a bad p

Execute Custom function in H2 Console

2017-07-13 Thread Lucky
Hi: As some reason,I must utilize custom function in query sql . Just like this: select myId('myRule'),sname from tableA I have define the custom function 'myid' with java code . And it work running on client node. But when I run the sql in H2 Console, it got the wrong

Re:Re: Requested array size exceeds VM limit

2017-07-12 Thread Lucky
Actually,my setting is : Xms =40G,Xmx =120G. but it still got the wrong message. Are there another parameters about H2 console? Thanks. Lucky At 2017-07-12 16:53:56, "Humphrey" wrote: >You can modify the ignite.sh script and increase the Xms and values > > > > &g

Re:How to start up H2 Console

2017-07-12 Thread Lucky
OK,I understand. Now is still do not support remote connection, just local. Do it will be supported in the future? Thanks . Lucky At 2017-07-12 15:51:46, "Humphrey" wrote: >I didn't get that error when I tried it out on my computer. It started Ignite >and opened th

Requested array size exceeds VM limit

2017-07-12 Thread Lucky
Hi: I have a table with 2000 records, 6 fields. When I use "select fid from userInfo " ,It got a error,like this: Exception in thread "H2 Console thread" java.lang.OutOfMemoryError: Requested array size exceeds VM limit How to increase the heap? Thanks Lucky

Re:Re: Re:Re: How to start up H2 Console

2017-07-11 Thread Lucky
Thank you for your reply. I did as you suggested in the mail. but on accessing the url I get an error "Sorry, remote connections ('webAllowOthers') are disabled on this server.". How do I pass "webAllowOthers" parameter to h2 database through ignite? Thanks

Re:Re: How to start up H2 Console

2017-07-11 Thread Lucky
Yes,I had study the document many times. But the document is too simple. I still have two question: 1.How to set the IGNITE_H2_DEBUG_CONSOLE property? modified ignite.sh ? Maybe a particular setting is perfect to me. 2.what is the URL if I open browser? By the way,the web console is too heavy fo

How to start up H2 Console

2017-07-10 Thread Lucky
Hi: I want to analysis sql explain and debug sql . How to start up H2 Console? My server OS is centos6. IP is 192.168.1.2 Thanks.

ask question about ignite

2017-07-10 Thread Lucky