claim will lead to message ttl smaller

[yangzhenyu]

In order to avoid the expiration of the message is deleted, when the message is still claim status.
In this case, zaqar will modifies the message ttl. But the ttl gets smaller (currently this ttl=claim_ttl+claim_grace) and may be less than age. I think this is a problem, and it should use ttl=ttl+claim_ttl+claim_grace.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/517901

[OpenStack Infra (hudson-openstack)]

Change abandoned by yangzhenyu (<email address hidden>) on branch: master
Review: https://review.openstack.org/517901

[yangzhenyu (cdyangzhenyu)]

But this ttl for each message may not be the same, only get a message from backend and then modify it, so there is a considerable performance consumption, so give up here to modify.

[Feilong Wang (flwang)]

Thanks for opening this bug. It's a very interesting question. I'm just trying to answer it from my PoV. The message TTL is only to make sure the message could be lived until it's consumed by a client. So that's said once it's processed by a client, message TTL is not necessary to be kept as the original value. But I totally understand your point here. I will think about this and comparing the behaviours on other messaging services. Will revisit this bug soon. Thanks.

[OpenStack Infra (hudson-openstack)]

Change abandoned by wanghao (<email address hidden>) on branch: master
Review: https://review.opendev.org/517901
Reason: Since there isn't update for a long time, will abandon this. Please feel free to restore it if someone still work on this.