You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Ilya Kasnacheev <il...@gmail.com> on 2019/01/28 11:13:05 UTC
Re: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES
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 <ma...@gmail.com>:
> 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 seems to
> limit the height.
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Re: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES
Posted by Ilya Kasnacheev <il...@gmail.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 г. в 07:30, mahesh76private <ma...@gmail.com>:
> 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 index huge, ran into 100s of Gig...
>
> Anyway, we are not using this option anymore.... Frankly, it seems a
> internal detail of ignite, and not sure why this is given as an option to
> configure for users.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Re: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES
Posted by "ilya.kasnacheev" <il...@gmail.com>.
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
Posted by mahesh76private <ma...@gmail.com>.
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 index huge, ran into 100s of Gig...
Anyway, we are not using this option anymore.... Frankly, it seems a
internal detail of ignite, and not sure why this is given as an option to
configure for users.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES
Posted by mahesh76private <ma...@gmail.com>.
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.nabble.com/processDynamicIndexChange-exception-at-client-node-while-creating-index-td26770.html
My suspicion is this issue happens only when table is partitioned, no
affinity keys, and definitely spread across multiple nodes.
Please review the logs
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/