You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bookkeeper.apache.org by "Apurva007 (via GitHub)" <gi...@apache.org> on 2023/03/07 08:07:04 UTC

[GitHub] [bookkeeper] Apurva007 opened a new issue, #3845: Force GC API PUT Call fails with Internal Server Error

Apurva007 opened a new issue, #3845:
URL: https://github.com/apache/bookkeeper/issues/3845

   **BUG REPORT**
   
   Force GC API PUT call fails with Internal Server Error
   
   A clear and concise description of what the bug is.
   
   1. Create a Bookkeeper cluster of 5 nodes
   2. Run the PUT request: curl  --request PUT '{IP}:8000/api/v1/bookie/gc'
   
   Expected Behavior:
   200 should be returned by the bookie
   
   Bookie Version: 4.15.3
   


-- 
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@bookkeeper.apache.org.apache.org

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

[GitHub] [bookkeeper] Apurva007 commented on issue #3845: Force GC API PUT Call fails with Internal Server Error

Posted by "Apurva007 (via GitHub)" <gi...@apache.org>.
Apurva007 commented on issue #3845:
URL: https://github.com/apache/bookkeeper/issues/3845#issuecomment-1469314553

   @BewareMyPower Thanks for the response. The curl command worked on my cluster and the GC was triggered.
   
   @hangc0276 I can also confirm that there were no error logs on the bookie server when the "internal server error" was thrown.
   
   I really appreciate the help. @BewareMyPower / @hangc0276 .
   
   I am happy to help with a PR for the documentation changes if you point me to the location. 
   


-- 
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@bookkeeper.apache.org

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

[GitHub] [bookkeeper] hangc0276 commented on issue #3845: Force GC API PUT Call fails with Internal Server Error

Posted by "hangc0276 (via GitHub)" <gi...@apache.org>.
hangc0276 commented on issue #3845:
URL: https://github.com/apache/bookkeeper/issues/3845#issuecomment-1463426712

   Hi @Apurva007, thanks for reporting this issue. Would you please share the bookie server's log?


-- 
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@bookkeeper.apache.org

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

[GitHub] [bookkeeper] BewareMyPower commented on issue #3845: Force GC API PUT Call fails with Internal Server Error

Posted by "BewareMyPower (via GitHub)" <gi...@apache.org>.
BewareMyPower commented on issue #3845:
URL: https://github.com/apache/bookkeeper/issues/3845#issuecomment-1467568830

   You have to pass the JSON data, e.g.
   
   ```bash
   curl -L http://localhost:8009/api/v1/bookie/gc -X PUT -H 'Content-Type: application/json' -d '{"is_in_force_gc": "true"}'
   ```
   
   P.S. My BK HTTP server listens on port 8009.
   
   BTW, there is no log in the bookie server. /cc @hangc0276 


-- 
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@bookkeeper.apache.org

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

Re: [I] Force GC API PUT Call fails with Internal Server Error [bookkeeper]

Posted by "Apurva007 (via GitHub)" <gi...@apache.org>.
Apurva007 closed issue #3845: Force GC API PUT Call fails with Internal Server Error
URL: https://github.com/apache/bookkeeper/issues/3845


-- 
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@bookkeeper.apache.org

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