Gopal Holla
Gopal Holla
@maciejbak85 About the internal server error, anything in the logs (frontend or server)? Internal server errors usually get logged
well thats odd - all internal server errors on the frontend get logged. You can also check the public access logs to make sure the request was received and recorded....
I'm not familiar with docker but the from the error message I can glean that the frontend is unable to connect to the server. It might be some port binding...
The compaction code has not run at this point. This happened during the setup of the test (create a log, index etc). I'll add some log messages but this seems...
@cgtz #856
#721 fixes the bug but tests to test this scenario need to be added to `BlobStoreStats`
Sorry for the late reply. I'll take a look at how this can be done.
We will probably release a version once the `NonBlockingRouter` is stable (another month or so). Does that work for you?
Great idea ! Do you have any ideas on how this can integrated into the Router API? Are you thinking of a new API or modifications to the return type...
I wonder if you can simply change `GetBlobResultInternal` into `GetBlobResult`? Also, let's have a more descriptive name than `SubBlobKeys`. `ChunkBlobIds` seems more in line with the terminology we use.