----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/66336/#review200210 -----------------------------------------------------------
sentry-provider/sentry-provider-db/src/main/java/org/apache/sentry/provider/db/service/persistent/CounterWait.java Lines 191 (patched) <https://reviews.apache.org/r/66336/#comment280863> can you put the currentId in the log message? That would be helpful sentry-provider/sentry-provider-db/src/main/java/org/apache/sentry/provider/db/service/persistent/CounterWait.java Lines 203 (patched) <https://reviews.apache.org/r/66336/#comment280864> Can you put the currentId in log message? sentry-provider/sentry-provider-db/src/main/java/org/apache/sentry/provider/db/service/persistent/CounterWait.java Lines 214 (patched) <https://reviews.apache.org/r/66336/#comment280865> can you put currentId in log message to help correlate the events? - Na Li On March 29, 2018, 5:25 p.m., kalyan kumar kalvagadda wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/66336/ > ----------------------------------------------------------- > > (Updated March 29, 2018, 5:25 p.m.) > > > Review request for sentry and Na Li. > > > Bugs: SENTRY-2190 > https://issues.apache.org/jira/browse/SENTRY-2190 > > > Repository: sentry > > > Description > ------- > > Debug logging in CounterWait is not good enough to actually an issue around > this area. It's a good idea to extend the current logging. > > > Diffs > ----- > > > sentry-provider/sentry-provider-db/src/main/java/org/apache/sentry/provider/db/service/persistent/CounterWait.java > d8c82970b56b1599a07f0e26edab8ed3d59b9948 > > > Diff: https://reviews.apache.org/r/66336/diff/2/ > > > Testing > ------- > > > Thanks, > > kalyan kumar kalvagadda > >
