Thanks for the answers!
As it leads to a decrease of caching efficiency, i've opened an issue:
http://tracker.ceph.com/issues/22528
15.12.2017, 23:03, "Gregory Farnum" :
> On Thu, Dec 14, 2017 at 9:11 AM, Захаров Алексей
> wrote:
>> Hi, Gregory,
>>
On Thu, Dec 14, 2017 at 9:11 AM, Захаров Алексей wrote:
> Hi, Gregory,
> Thank you for your answer!
>
> Is there a way to not promote on "locking", when not using EC pools?
> Is it possible to make this configurable?
>
> We don't use EC pool. So, for us this meachanism is
Hi, Gregory,Thank you for your answer! Is there a way to not promote on "locking", when not using EC pools?Is it possible to make this configurable? We don't use EC pool. So, for us this meachanism is overhead. It only adds more load on both pools and network. 14.12.2017, 01:16, "Gregory Farnum"
Voluntary “locking” in RADOS is an “object class” operation. These are not
part of the core API and cannot run on EC pools, so any operation using
them will cause an immediate promotion.
On Wed, Dec 13, 2017 at 4:02 AM Захаров Алексей
wrote:
> Hello,
>
> I've found that
Hello,
I've found that when client gets lock on object then ceph ignores any promotion
settings and promotes this object immedeatly.
Is it a bug or a feature?
Is it configurable?
Hope for any help!
Ceph version: 10.2.10 and 12.2.2
We use libradosstriper-based clients.
Cache pool settings: