Re: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES

2019-01-31 Thread ilya.kasnacheev
Hello! I have filed an usability ticket https://issues.apache.org/jira/browse/IGNITE-11162 Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES

2019-01-31 Thread Ilya Kasnacheev
Hello! Index inline is actually a vital parameter that can make up for multiple orders of performance difference. You can find threads about this in users list archive. However, you should definitely not set it to anything comparable to page size. Regards, -- Ilya Kasnacheev ср, 30 янв. 2019

Re: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES

2019-01-29 Thread mahesh76private
On further debug, we realised we set index inline option to 2048..while creating index. This problem (LOCK_RETRIES issue) started only after that. Before, that we didn't face much of a problem with indexes. Also, another notable observation is setting index inline option to 2048 also made the

Re: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES

2019-01-28 Thread mahesh76private
We actually think while building index, the tree is getting corrupted. Increasing LOCK_RETRIES didnt fix it too... Please review the below link as well. Infact, we saw creating index was getting into a infinite loop and throwing out errors at other clients.

Re: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES

2019-01-28 Thread Ilya Kasnacheev
Hello! This is highly unusual, I guess the default value for this property should be far larger that anything attainable in practice. Dmitriy, Alexey, can you please clarify? Regards. -- Ilya Kasnacheev вс, 27 янв. 2019 г. в 21:16, mahesh76private : > Increasing the size of

RE: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES

2019-01-27 Thread mahesh76private
Increasing the size of IGNITE_BPLUS_TREE_LOCK_RETRIES makes the issue go away. But the explanation that is occurs due to contention is somewhat not clear. In all cases, in occurred to be when I was creating an index. Feels like it is somehow related to the height of the tree... and this

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

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

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/

RE: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES

2019-01-16 Thread Stanislav Lukyanov
to the IGNITE_BPLUS_TREE_LOCK_RETRIES property (e.g. 10). If you see still see the exception then it’s a corruption. If you don’t – it’s a contention. Stan From: mahesh76private Sent: 16 января 2019 г. 7:48 To: user@ignite.apache.org Subject: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES

failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES

2019-01-15 Thread mahesh76private
On 2.7, we are regularly seeing the below message and then the nodes stop. [16:45:04,759][SEVERE][disco-event-worker-#63][] JVM will be halted immediately due to the failure: [failureCtx=FailureContext [type=CRITICAL_ERROR, err=class o.a.i.IgniteCheckedException: Maximum number of retries 1000