You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2022/05/20 10:48:16 UTC

[GitHub] [pulsar] wojtekkedzior commented on issue #15332: ledgers not getting deleted when disk used exceeds threshold on all bookies

wojtekkedzior commented on issue #15332:
URL: https://github.com/apache/pulsar/issues/15332#issuecomment-1132758568

   Right, so after playing around with this a bit I realise that the only way to get out of this scenario is to scale your resources, if you can.   In case you cannot scale becuase you are at the limit of your hardware, then you have to decommission the bookies and bring them back that way.  Since the cluster is not usable anyway it doesn't really matter that your are going to decommission them.
   I also found a setting called: isForceGCAllowWhenNoSpace.  which should take care of this issue, but I have not tested it yet.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org