Highest Description
Motivated by NETVIRT-916, but much more widely applicable in general, and based on https://lists.opendaylight.org/pipermail/controller-dev/2017-December/014100.html, we should reduce the ConcurrentDOMDataBroker's TX failure logging from WARN to DEBUG, and add @CheckReturnValue to WriteTransaction submit(), because it should be up to the caller to decide whether or not to log this at as a WARN, ERROR or not at all (e.g. if it is going to retry).
Attachments
Issue Links
- relates to
-
CONTROLLER-1855 Controller should not error log any OptimisticLockFailedException which applications actually handle
-
- Resolved
-
-
TSC-100 WriteTransaction.submit() to be annotated with @CheckReturnValue
-
- Resolved
-
| # | Subject | Branch | Project | Status | CR | V |
|---|---|---|---|---|---|---|
| 66355,2 | JobCoordinator should log failures DEBUG not WARN if there are retries | master | infrautils | Status: MERGED | +2 | +1 |
| 66360,5 | AsyncWriteTransaction submit() with @CheckReturnValue | master | controller | Status: MERGED | +2 | +1 |
| 66361,7 | AsyncWriteTransaction submit() with @CheckReturnValue | master | mdsal | Status: MERGED | +2 | +1 |
| 66362,1 | ConcurrentDOMDataBroker LOG debug instead of error | master | controller | Status: MERGED | +2 | +1 |
| 66634,3 | Fix JobCoordinator logging if there are retries | master | infrautils | Status: MERGED | +2 | +1 |
| 68080,2 | ConcurrentDOMDataBroker LOG debug instead of error | stable/nitrogen | controller | Status: MERGED | +2 | +1 |
| 68081,2 | ConcurrentDOMDataBroker LOG debug instead of error | stable/carbon | controller | Status: MERGED | +2 | +1 |
