Force GC API PUT Call fails with Internal Server Error

[Apurva007]

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

[hangc0276]

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

[BewareMyPower]

The document here missed something that you have to pass the JSON data, e.g.

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

[Apurva007]

@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.

[fantastywusheng]

Why am I getting 'Resource not found'? My Pulsar version is 2.3.0 and my bookie version is 4.9.0.
I'm looking at the official documentation where the closest version listed is 4.9.2, but I'm unable to determine if version 4.9.0 supports the feature.