Ignite node failed for no obvious reason

2018-07-24 Thread Ray
I have a three node Ignite 2.6 cluster setup with the following config.

Ignite data can't be recovered after node fail

2018-07-24 Thread Ray
Following node fail described in this thread http://apache-ignite-users.70518.x6.nabble.com/Ignite-node-failed-for-no-obvious-reason-td22866.html, I tried to reboot this node and recover the data to make Ignite cluster available again. First, I try reboot node2 directly but failed. The node log is

Re: Waiting too long, to load 7k datas to cache.... And Client gets null value

2018-07-24 Thread monstereo
thank you, As you stated, it is about my memory configuration, I solved it. (When I increase the memory) But can you explain external synch. part for " "cache is not ready" if the cache is already created but not populated yet. You need external sync here." Which method ignite provides for this "

Re: Random-LRU-2 ?

2018-07-24 Thread monstereo
I could not understand this part "MIN(timestamp1, timestamp2) for further comparing" That's means : Algorithm select randomly 5 indexes(let's say it choose indexes 4, 12, 5, 1, 3) and takes the index MIN(timestamp1, timestamp2) (let's say index 5) Then it evaluates |timestamp1 - timestamp2| for

Re: Java API for SQL queries

2018-07-24 Thread Maxim Malygin
Hi Evgenii, Thanks for the answer. Unfortunately it seems it does matter. If I do a query inside a transaction and use an instance of a cache that differs of a cache inside the query, I will get the following exception (note I do it on client node): Exception in thread "main" javax.cache.CacheExc

RE: Random-LRU-2 ?

2018-07-24 Thread Stanislav Lukyanov
Random-LRY selects the minimum of 5 timestamps (5 pages, 1 timestamp for each page). Random-2-LRU selects the minimum of 10 timestamps (5 pages, 2 timestamps for each page). My advice is not to go that deep. Random-2-LRU I protected from the “one-hit wonder” and has a very tiny overhead compar

Re: Java API for SQL queries

2018-07-24 Thread Evgenii Zhuravlev
I'm not sure that this case is valid at all right now, since as for now, Ignite doesn't support transactions for SQL. Evgenii 2018-07-24 13:36 GMT+03:00 Maxim Malygin : > Hi Evgenii, > > Thanks for the answer. > Unfortunately it seems it does matter. If I do a query inside a > transaction and us

Re: Ignite node failed for no obvious reason

2018-07-24 Thread Evgenii Zhuravlev
Hi, Are you sure that you have the full connectivity between all nodes? I mean server and client nodes. There are a lot of different exceptions like "err=No route to host" in the log, which definitely points to the network problems. At the same time, if you think that it was just a short-time out

odbc - conversion failed because data value overflowed

2018-07-24 Thread wt
I have a SQL server instance and configured odbc driver and a linked server. I noticed the linked server doesn't show any columns and in fact can't retrieve a list of columns. Secondly, if i query the data source i get a data overflow error. any idea 1.png

RE: odbc - conversion failed because data value overflowed

2018-07-24 Thread Stanislav Lukyanov
Are you trying to use MS SQL tools to connect to Ignite? I don’t think that’s possible – at least, Ignite doesn’t claim to support that. Stan From: wt Sent: 24 июля 2018 г. 16:01 To: user@ignite.apache.org Subject: odbc - conversion failed because data value overflowed I have a SQL server instan

RE: odbc - conversion failed because data value overflowed

2018-07-24 Thread wt
yes but i would have thought the ODBC driver would be compatible through odbc interface standards. It would be nice to be able to add a linked server in MSSQL and query ignite. I might have to fudge it and create a .net CLR -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Composite Queries

2018-07-24 Thread musclesonvacation
Hi, I'm developing in C#. i want to pull a composite type consisting of partial fields from 4 tables. I have these tables defined in an ignite node. I can run a sql query through the vizor console and get the results expected. moving to the client i'm not sure how to set this up. do i need to d

Re: Can wal archive be deleted?

2018-07-24 Thread Mikhail
Hi Ray, it's not safe to remove archive, in release 2.7 ignite will be able to do this: https://issues.apache.org/jira/browse/IGNITE-7912 ... Delete unused archived wal segments on each node: control.sh [--host HOST_OR_IP] [--port PORT] [--user USER] [--password PASSWORD] [--ping-interval

RE: odbc - conversion failed because data value overflowed

2018-07-24 Thread Stanislav Lukyanov
I don’t know how that MSSQL studio works, but it might be dependent on T-SQL or some system views/tables specific for MSSQL. DBeaver doesn’t use any DB-specific features and is known to work with Ignite. Take a look at this page: https://apacheignite-sql.readme.io/docs/sql-tooling Stan From: wt

Re: Java API for SQL queries

2018-07-24 Thread Maxim Malygin
Really? How about DML statements? Regards, Maxim вт, 24 июл. 2018 г. в 15:06, Evgenii Zhuravlev : > I'm not sure that this case is valid at all right now, since as for now, > Ignite doesn't support transactions for SQL. > > Evgenii > > 2018-07-24 13:36 GMT+03:00 Maxim Malygin : > >> Hi Evgenii,

Re: Java API for SQL queries

2018-07-24 Thread Evgenii Zhuravlev
I think transactional SQL should be released till the end of the summer 2018-07-24 17:41 GMT+03:00 Maxim Malygin : > Really? How about DML statements? > > Regards, > Maxim > > вт, 24 июл. 2018 г. в 15:06, Evgenii Zhuravlev : > >> I'm not sure that this case is valid at all right now, since as for

Re: Waiting too long, to load 7k datas to cache.... And Client gets null value

2018-07-24 Thread monstereo
?? monstereo wrote > thank you, > As you stated, it is about my memory configuration, I solved it. (When I > increase the memory) > > But can you explain external synch. part for " "cache is not ready" if the > cache is already created but not populated yet. You need external sync > here." > > W

Re: Batch insert into ignite

2018-07-24 Thread Michael Cherkasov
I can't say for sure which one should be better for sure, it must be benchmarked. But if you can use SqlFieldsQuery this means that you can use native Ignite API, right? So, in this case, IgniteDataStreamer would be the best choice. 2018-07-24

Re: Waiting too long, to load 7k datas to cache.... And Client gets null value

2018-07-24 Thread Ilya Kasnacheev
Hello! You can use ignite.countDownLatch(). I believe we've already discussed this approach. Regards, -- Ilya Kasnacheev 2018-07-24 18:14 GMT+03:00 monstereo : > ?? > > monstereo wrote > > thank you, > > As you stated, it is about my memory configuration, I solved it. (When I > > increase the

Re: Waiting too long, to load 7k datas to cache.... And Client gets null value

2018-07-24 Thread monstereo
thanks, ilya however, client does not wait until backup has complete. Here is the my codes: First I create node1, and wait until cache size is 2.000.000 Then i run another nodes (node2, client) and yes client will wait until 2 node2 runs But i want client to wait until backup operation is done.

Ignite Cluster with remote server + Cassandra Persistence

2018-07-24 Thread okiesong
How can I use Ignite cluster with remote servers? Currently, I am getting a below error. FYI, I have already configured my TcpDiscoveryVmIpFinder and TcpCommunicationSpi correctly, but for some reason, it is pointing at 10.209.236.58 which is from localhost, and thus the server is not able to con

Errors with TCPCommunicationSpi when using zookeeper discovery

2018-07-24 Thread lmark58
When using zoo keeper discovery I am getting intermittent errors with clients connecting. Scenario - I have one ignite server running, try to connect with 4 clients. For one of the connecting clients the socket between the client and server is never established and the log repeats the message o.a

Re: Ignite Cluster with remote server + Cassandra Persistence

2018-07-24 Thread Вячеслав Коптилин
Hello, It does not seem to me, that the issue is somehow related to the thread you mentioned. I bet the root cause of the problem is a misconfiguration. At least, the exception message tells me that CassandraCacheStore class cannot be initialized for some reason: java.lang.NullPointerException

Re: Ignite node failed for no obvious reason

2018-07-24 Thread Ray
Hi, All nodes are all inter-connectable. I think it's a short time outage in network because earlier data ingesting is successful until the network glitch. I'll try to build with IGNITE-8739 and try again. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Batch insert into ignite

2018-07-24 Thread Sriveena Mattaparthi
Thanks for the clarification Michael..will try the streamer option. Regards, Sriveena From: Michael Cherkasov [mailto:michael.cherka...@gmail.com] Sent: Tuesday, July 24, 2018 9:49 PM To: user@ignite.apache.org Subject: Re: Batch insert into ignite I can't say for sure which one should be better