RE: Is there a way to allow overwrite when set streaming on?

2019-01-16 Thread Stanislav Lukyanov
Use `SET STREAMING ON ALLOW_OVERWRITE ON`. It’s a shame it’s not documented. Filed https://issues.apache.org/jira/browse/IGNITE-10952 for that. Stan From: yangjiajun Sent: 16 января 2019 г. 9:19 To: user@ignite.apache.org Subject: Is there a way to allow overwrite when set streaming on? Hello.

ignite continuous query with XML

2019-01-16 Thread shivakumar
is there a way to configure continuous query using spring XML? is there any example or reference for configuring continuous query with XML? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES

2019-01-16 Thread Stanislav Lukyanov
It means that Ignite couldn’t find the place it needed in a B+ tree in 1000 iterations. It could mean either that there is a high contention on the tree (it changes a lot, and one thread is unlucky and couldn’t keep up with the speed), or that the tree is corrupted. Try to set a larger value t

RE: ignite continuous query with XML

2019-01-16 Thread Stanislav Lukyanov
No, you have to use actual code. Stan From: shivakumar Sent: 16 января 2019 г. 11:08 To: user@ignite.apache.org Subject: ignite continuous query with XML is there a way to configure continuous query using spring XML? is there any example or reference for configuring continuous query with XML?

RE: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES

2019-01-16 Thread mahesh76private
how do I set it ? should I boot ignite node (ignite.sh) with the following switch ? java ... -DIGNITE_BPLUS_TREE_LOCK_RETRIES=10 regards Mahesh -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Does set streaming off command flush data?

2019-01-16 Thread yangjiajun
Hello. The ignite's doc says we should close the JDBC/ODBC connection so that all data is flushed to the cluster while use streaming mode.Does set streaming off command do the same so that we can reuse the connection? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES

2019-01-16 Thread Stanislav Lukyanov
Yes. You can also use an environment variable instead of the system property: IGNITE_BPLUS_TREE_LOCK_RETRIES=10 ignite.sh … Stan From: mahesh76private Sent: 16 января 2019 г. 11:29 To: user@ignite.apache.org Subject: RE: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES how do I set it ? sh

RE: Does set streaming off command flush data?

2019-01-16 Thread Stanislav Lukyanov
Yes. It closes the underlying streamers, which in turn flushes the data. Stan From: yangjiajun Sent: 16 января 2019 г. 11:41 To: user@ignite.apache.org Subject: Does set streaming off command flush data? Hello. The ignite's doc says we should close the JDBC/ODBC connection so that all data is f

RE: Baselined node rejoining crashes other baseline nodes - Duplicate KeyError

2019-01-16 Thread Stanislav Lukyanov
Hi, Left a comment in the issue. In short, the problem is that you got a duplicate index on one of your nodes somehow, even though it shouldn’t happen. Need to figure out, how. Can you tell what you do with the cluster when it is running? I’m particularly interested in any of the actions relate

Ignite Cache copy from another cache.

2019-01-16 Thread Hemasundara Rao
Hi Ignite Team, Is there a way to assign one cache with another cache ( total data to be copied). We have a requirement to replace existing cache with another cache. Let us say we have Cache1 ( loaded data from database). Every day we want to replace Cache1 with another Cache1_Refresh ( freshly lo

RE: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES

2019-01-16 Thread mahesh76private
OK. We don't have 1000 users for causing any sort of concurrency related lock ups. So possible explanation is corruption of the tree, below is our scenario -a- We created a table with sql - in the create params KEY_TYPE= ".", VALUE_TYPE="..." are also set. The intention is to retrieve data

RE: Baselined node rejoining crashes other baseline nodes - Duplicate KeyError

2019-01-16 Thread mahesh76private
Stan, thanks for the visibility. -1- Over the last year, we move from various versions of ignite 2.4, 2.5 to 2.7. I always keep work folder in tact. -2- Over a period of development, we might have tried to create index a second or many times on the same column on which an index already existed.

RE: Failing to create index on Ignite table column

2019-01-16 Thread Shravya Nethula
Hi Stan, Thank you! This information is helpful. Do you know any Ignite API through which I can get the indexes of a particular table? Regards, Shravya Nethula. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Thin client cannot retrieve data that was inserted with the regular Ignite client when using a composite key

2019-01-16 Thread Roman Shtykh
Thin client cannot retrieve data with the composite key when it is put by a regular (thick) Ignite client. Is any additional configuration needed or is it a bug?     import java.io.Serializable;     import org.apache.ignite.Ignite;     import org.apache.ignite.IgniteCache;     import org.apache

Re: Recovering from a data region OOM condition

2019-01-16 Thread colinc
We were using Ignite 2.4 (update pending). Ignite 2.5 and later seens to treat OOM as a critical error by default and stops the node. The reproducer below uses a failure handler to stop this from happening. It allocates a 100MB (configurable - 100MB is quite small) region and fills it up with data.

Re: Do we require to set MaxDirectMemorySize JVM parameter?

2019-01-16 Thread colinc
Thanks. We'll give Native Persistence another try. Our reluctance to use it stems from the fact that if something goes wrong with the storage then there are additional production processes required to recover - bad persistent store can cause the cluster to fail to start or else propagate problems.

Re: Do we require to set MaxDirectMemorySize JVM parameter?

2019-01-16 Thread rick_tem
Yes, we have a similar reluctance to use persistent store. Ouruse case is that Gigs of data will be running through it with several caches that we don't necessarily want to keep around in a docker environment. Some caches, however, we would like persistent. Is there a plan to have persistence co

ignite_backup_restore_query

2019-01-16 Thread Prerana y
I was trying to backup and restore the ignite persistence and wal data . Are there any steps available that can be followed to restore the data to pods. Thanks and regards Prerana

RE: Failing to create index on Ignite table column

2019-01-16 Thread Stanislav Lukyanov
Don’t think there is any Ignite API for that yet. Stan From: Shravya Nethula Sent: 16 января 2019 г. 12:42 To: user@ignite.apache.org Subject: RE: Failing to create index on Ignite table column Hi Stan, Thank you! This information is helpful. Do you know any Ignite API through which I can get

Data streamer has been closed.

2019-01-16 Thread yangjiajun
Hello. I do test on a ignite 2.6 node with persistence enabled and get an exception: Exception in thread "main" java.sql.BatchUpdateException: class org.apache.ignite.IgniteCheckedException: Data streamer has been closed. at org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$Stream

Re: Failed to wait for partition map exchange on cluster activation

2019-01-16 Thread Ilya Kasnacheev
Hello! I can see multiple "Failed to process selector key" errors in your log. Are you sure that your nodes can communicate via network freely and without delay? Regards, -- Ilya Kasnacheev вт, 15 янв. 2019 г. в 20:12, Andrey Davydov : > Hello, > > You can find full log there: > https://drive

Re: Failed to wait for partition map exchange on cluster activation

2019-01-16 Thread Ilya Kasnacheev
Hello! Sorry, wrong thread:) It is hard to say what happens here exactly. Can you collect several thread dumps during this prolonged activation, share them with us? Do you have e.g. services? I was told that services would start during activation. Regards, -- Ilya Kasnacheev ср, 16 янв. 2019

Re: Concurrent merge into operations cause critical system error on ignite 2.7 node.

2019-01-16 Thread Ilya Kasnacheev
Hello! I can see multiple "Failed to process selector key" errors in your log. Are you sure that your nodes can communicate via network freely and without delay? Regards, -- Ilya Kasnacheev ср, 16 янв. 2019 г. в 10:21, yangjiajun <1371549...@qq.com>: > Hello. > > Please see the logs. > > igni

Re: Do we require to set MaxDirectMemorySize JVM parameter?

2019-01-16 Thread Ilya Kasnacheev
Hello! You can have some caches persistent and some not persistent, by having several DataRegions some of whose have persistenceEnabled=true and some are not, and specifying DataRegion by name in cache configuration. Please see https://apacheignite.readme.io/docs/memory-configuration#section-data

Re: Concurrent merge into operations cause critical system error on ignite 2.7 node.

2019-01-16 Thread yangjiajun
Hello. Thanks for reply.I think these "Failed to process selector key" errors cause by the manual halt of my test application.I don't think network is a problem.Since my test cases show that some operations cause trouble while some others work fine. ilya.kasnacheev wrote > Hello! > > I can see

Re: Do we require to set MaxDirectMemorySize JVM parameter?

2019-01-16 Thread rick_tem
Oh, that is great. I wasn't aware of that. Thanks for the link! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Concurrent merge into operations cause critical system error on ignite 2.7 node.

2019-01-16 Thread Ilya Kasnacheev
Hello! Can you provide a reproducer project which would reliably show this behavior? Regards, -- Ilya Kasnacheev ср, 16 янв. 2019 г. в 15:37, yangjiajun <1371549...@qq.com>: > Hello. > > Thanks for reply.I think these "Failed to process selector key" errors > cause > by the manual halt of my

Re: Data streamer has been closed.

2019-01-16 Thread Ilya Kasnacheev
Hello! I can reproduce this problem, but then again, it does not seem to reproduce on 2.7. Have you considered upgrading? Regards, -- Ilya Kasnacheev ср, 16 янв. 2019 г. в 14:14, yangjiajun <1371549...@qq.com>: > Hello. > > I do test on a ignite 2.6 node with persistence enabled and get an >

RE: Failed to wait for partition map exchange on cluster activation

2019-01-16 Thread Andrey Davydov
No, I don’t start services during activation (because I got some problems with it on older ignite some months ago). There is one broadcasted service in system, and I start it manually just after activation. I will provide dumps and more detailed logs bit later. Andrey. От: Ilya Kasnacheev Отпр

failed to connect to secure ignite server from ignite web agent

2019-01-16 Thread shivakumar
Iam trying to connect to ignite server from web agent but it is giving the below exception: [2019-01-15 15:54:13,684][INFO ][pool-1-thread-1][RestExecutor] Connected to cluster [url=https://ignite-service.default.svc.cluster.local:8080] [2019-01-15 15:54:13,720][WARN ][pool-1-thread-1][ClusterList

NearCache

2019-01-16 Thread Grégory Jevardat de Fombelle
Hello Is there any option to have a nearCache in Ignite that store unMarschalled values instead of serialized ones. I ask this for performance reasons. I noticed that for big cached objects, default Java unserialization is quite expensive, like ~ 2 secs for a complex > 100MB object. So in the

Re: failed to connect to secure ignite server from ignite web agent

2019-01-16 Thread Alexey Kuznetsov
Hi, Shivakumar! If you want to connect to cluster with enabled security you need to configure following properties on Web Agent: "--node-login" and "--node-password" via command line or "default.properties" file. [1] For example: ignite-web-agent.sh --node-login ignite --node-password ignite Pl

Transactional cache in Atomic mode

2019-01-16 Thread msuh
Hi, Two questions about transactionality and locking: 1) I've been looking at https://apacheignite.readme.io/docs/transactions and couldn't get a clear answer from the Ignite documentation so I hope to get an answer here. All of the caches we use are set to TRANSACTIONAL, as we will often need to

Re: Transactional cache in Atomic mode

2019-01-16 Thread Mikhail
Hi >1) you can do all operations on transaction caches without defining an explicit transaction. However, even if you don't start transaction and for example put some data in transactional cache, ignite itself will make implicit transaction, so transactionCache.put("key", "value") -> will update y

Re: Failed to wait for partition map exchange on cluster activation

2019-01-16 Thread Andrey Davydov
I create small reproducer project/ It is available on: https://drive.google.com/file/d/1A2_i1YBI7OGtJM0b8bxuIJrTI61ZQXoR/view?usp=sharing Thera are project, and some logs and dumps in archive. There is only one DemoTest.java to run to reproduce. test run 3 ignite nodes with configuration very si

Re: Transactional cache in Atomic mode

2019-01-16 Thread msuh
Hi Mikhail, Thanks for your answer. 1) So if Ignite implicitly puts each cache update in a transaction, does that mean it's just better performance-wise to wrap 100k updates in a transaction (We found that 100k was the optimal number of updates to do in a single transaction) than to not explicitl

RE: ignite continuous query with XML

2019-01-16 Thread shivakumar
thanks stan!! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

3rd party persistence with hive not updating hive with all records/entries in ignite

2019-01-16 Thread shivakumar
Hi i am trying to use hive as 3rd party persistence store and enabled write behind and i set these cache configurations using spring xml every 5000ms interval ignite updating only one recored

Re: ignite_backup_restore_query

2019-01-16 Thread Mikhail
Hi, you can make snapshots manually: 1. deactivate cluster. 2. stop all nodes 3. copy work, wal and data storage directories 4. start cluster again. To make live snapshots of your cluster you can use 3rd party solutions like this one https://docs.gridgain.com/docs/data-snapshots Thanks, Mike.

Re: ignite_backup_restore_query

2019-01-16 Thread msuh
Are there any additional steps to take after 4. start cluster again to ensure that ignite recognizes the new data? I've attempted several times to copy the data and wal directory (and making sure that the consistent ID are the same) into a new node, but when looking through visor, all the caches

Re: Thin client cannot retrieve data that was inserted with the regular Ignite client when using a composite key

2019-01-16 Thread Mikhail
Hi Roman, it looks like a bug for me, at least I don't see anything wrong about your test case. Also, I can reproduce the issue with the latest master version, so I filed a ticket: https://issues.apache.org/jira/browse/IGNITE-10960 Thank you for your report, Mike. -- Sent from: http://apache-i

Re: Ignite Cache copy from another cache.

2019-01-16 Thread Mikhail
Hi Hemasundara, I think this should be implemented on the application level. when a new cache is ready, you need to change the cache name that your app uses to make all operations use a new cache, might be this will require some synchronization, it depends on your requirements. Thanks, Mike. -

Re: MVCC and continuous query

2019-01-16 Thread Cindy Xing
Thanks Ilya. Do we have example show case the pub/sub programming model with MVCC enabled? Basically instead of pulling but react in case of update on specific key. Also, does ignite client API expose the version info.? Cindy -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Concurrent merge into operations cause critical system error on ignite 2.7 node.

2019-01-16 Thread yangjiajun
Hello. Here is my test code: import java.sql.Connection; import java.sql.DriverManager; import java.sql.PreparedStatement; import java.sql.SQLException; import java.sql.Statement; import java.util.Properties; /** * concurrent merge into * */ public class MergeInto { private final sta

Re: Data streamer has been closed.

2019-01-16 Thread yangjiajun
Hello. Thanks for reply.Unfortunately,I still get the exception after running my test on 2.7 for several times. ilya.kasnacheev wrote > Hello! > > I can reproduce this problem, but then again, it does not seem to > reproduce > on 2.7. Have you considered upgrading? > > Regards, > -- > Ilya K

server ignite.sh always shutdown

2019-01-16 Thread hulitao198758
Ignite. Sh start multi-node server side is very unstable, often appear process termination situation, I now is running on a server three cluster nodes, three servers make up three cluster environment, often a server node will hang, I do not know what situation -- Sent from: http://apache-ignite-

server ignite.sh always shutdown

2019-01-16 Thread hulitao198758
Ignite. Sh start multi-node server side is very unstable, often appear process termination situation, I now is running on a server three cluster nodes, three servers make up three cluster environment, often a server node will hang, I do not know what situation -- Sent from: http://apache-ignite-

server always shutdown

2019-01-16 Thread hulitao198758
Ignite. Sh start multi-node server side is very unstable, often appear process termination situation, I now is running on a server three cluster nodes, three servers make up three cluster environment, often a server node will hang, I do not know what situation -- Sent from: http://apache-ignite-

Re: WAL size control

2019-01-16 Thread Denis Magda
Justin, check this section, you can tun WAL or disable WAL archiving in general: https://apacheignite.readme.io/docs/write-ahead-log#section-tuning-wal-archive - Denis On Mon, Jan 14, 2019 at 7:06 PM Justin Ji wrote: > I have more than three hundred WAL segments in our folder >