Descriptions of the changes in this PR:

 - MDC context is passed to runnables, callables etc.
 - protocol extended, context is sent to bookie servers, restored there and 
back on client with the response.
   Hopefully did not miss some nuance on the server side, largely rely on 
changes in ordered executors to do all the magic.
 - did microbenchmarking of the protocol changes (strings added to protobuf, 
MDC context preserved/restored). Looks ok.
 - added unit tests.

(@bug W-5291641@) 
(@bug W-5291648@)


### Motivation

Troubleshooting of request-level failures/errors can be simplified if request 
id was passed through all the stages of the request, from threadpools on the 
client to bookies to the response back on the client. 
Log4j/Slf4j allows logging of MDC data so it makes sense to use this 
functionality for logging.

### Changes

 - MDC context is passed to runnables, callables etc.
 - protocol extended, context is sent to bookie servers, restored there and 
back on client with the response.
   Hopefully did not miss some nuance on the server side, largely rely on 
changes in ordered executors to do all the magic.
 - did microbenchmarking of the protocol changes (strings added to protobuf, 
MDC context preserved/restored). Looks ok.
 - added unit tests.

Master Issue: #850 

> ---
> In order to uphold a high standard for quality for code contributions, Apache 
> BookKeeper runs various precommit
> checks for pull requests. A pull request can only be merged when it passes 
> precommit checks. However running all
> the precommit checks can take a long time, some trivial changes don't need to 
> run all the precommit checks. You
> can check following list to skip the tests that don't need to run for your 
> pull request. Leave them unchecked if
> you are not sure, committers will help you:
>
> - [ ] [skip bookkeeper-server bookie tests]: skip testing 
> `org.apache.bookkeeper.bookie` in bookkeeper-server module.
> - [ ] [skip bookkeeper-server client tests]: skip testing 
> `org.apache.bookkeeper.client` in bookkeeper-server module.
> - [ ] [skip bookkeeper-server replication tests]: skip testing 
> `org.apache.bookkeeper.replication` in bookkeeper-server module.
> - [ ] [skip bookkeeper-server tls tests]: skip testing 
> `org.apache.bookkeeper.tls` in bookkeeper-server module.
> - [ ] [skip bookkeeper-server remaining tests]: skip testing all other tests 
> in bookkeeper-server module.
> - [ ] [skip integration tests]: skip docker based integration tests. if you 
> make java code changes, you shouldn't skip integration tests.
> - [ ] [skip build java8]: skip build on java8. *ONLY* skip this when *ONLY* 
> changing files under documentation under `site`.
> - [ ] [skip build java9]: skip build on java9. *ONLY* skip this when *ONLY* 
> changing files under documentation under `site`.
> ---

> ---
> Be sure to do all of the following to help us incorporate your contribution
> quickly and easily:
>
> If this PR is a BookKeeper Proposal (BP):
>
> - [ ] Make sure the PR title is formatted like:
>     `<BP-#>: Description of bookkeeper proposal`
>     `e.g. BP-1: 64 bits ledger is support`
> - [ ] Attach the master issue link in the description of this PR.
> - [ ] Attach the google doc link if the BP is written in Google Doc.
>
> Otherwise:
> 
> - [ ] Make sure the PR title is formatted like:
>     `<Issue #>: Description of pull request`
>     `e.g. Issue 123: Description ...`
> - [ ] Make sure tests pass via `mvn clean apache-rat:check install 
> spotbugs:check`.
> - [ ] Replace `<Issue #>` in the title with the actual Issue number.
> 
> ---


[ Full content available at: https://github.com/apache/bookkeeper/pull/1672 ]
This message was relayed via gitbox.apache.org for [email protected]

Reply via email to