[I] Prune always removes GC lock [accumulo]

["ddanielr (via GitHub)" <gi...@apache.org>]

ddanielr opened a new issue, #6076:
URL: https://github.com/apache/accumulo/issues/6076

   **Describe the bug**
   The GC lock format includes additional information along with the host and port `GC_CLIENT=<HostAndPort>`
   This causes the ZooZap code to always fail the hostPortPredicate check for the GC and attempt to remove the service lock on `prune` operations. 
   
   **Versions (OS, Maven, Java, and others, as appropriate):**
    - Affected version(s) of this project: 2.1.4
   
   **To Reproduce**
   Steps to reproduce the behavior (or a link to an example repository that reproduces the problem):
   1. start a running GC process
   2. run ./accumulo-cluster prune --dry-run --gc
   3. See the log message showing the lock will be deleted.
   
   **Expected behavior**
   The GC lock is correctly excluded
   
   **Additional context**
   This can be handled in the ZooZap code for removing the GC lock 
   See #6073 for additional info.
   
   


-- 
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: notifications-unsubscribe@accumulo.apache.org.apache.org

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

Re: [I] Prune always removes GC lock [accumulo]

["ddanielr (via GitHub)" <gi...@apache.org>]

ddanielr closed issue #6076: Prune always removes GC lock
URL: https://github.com/apache/accumulo/issues/6076


-- 
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: notifications-unsubscribe@accumulo.apache.org

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