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/
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
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 in
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.
http://apache-ignite-users.70518.x6.
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 IGNITE_BPLUS_TREE
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 variable
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
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
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/
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
10 matches
Mail list logo
