[ https://issues.apache.org/jira/browse/HBASE-21242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16651726#comment-16651726 ]
Hadoop QA commented on HBASE-21242: ----------------------------------- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s{color} | {color:blue} Docker mode activated. {color} | | {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 6s{color} | {color:red} HBASE-21242 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/0.8.0/precommit-patchnames for help. {color} | \\ \\ || Subsystem || Report/Notes || | JIRA Issue | HBASE-21242 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12944137/0001-HBASE-21317-hbck2-Add-version-version-handling-and.patch | | Console output | https://builds.apache.org/job/PreCommit-HBASE-Build/14713/console | | Powered by | Apache Yetus 0.8.0 http://yetus.apache.org | This message was automatically generated. > [amv2] Miscellaneous minor log and assign procedure create improvements > ----------------------------------------------------------------------- > > Key: HBASE-21242 > URL: https://issues.apache.org/jira/browse/HBASE-21242 > Project: HBase > Issue Type: Bug > Components: amv2, Operability > Reporter: stack > Assignee: stack > Priority: Minor > Fix For: 3.0.0, 2.2.0, 2.1.1, 2.0.3 > > Attachments: > 0001-HBASE-21317-hbck2-Add-version-version-handling-and.patch, > HBASE-21242.addendum.fix.testhregioninfo.patch, > HBASE-21242.branch-2.0.001.patch, HBASE-21242.branch-2.0.001.patch, > HBASE-21242.branch-2.0.002.patch, HBASE-21242.branch-2.001.patch, > HBASE-21242.branch-2.001.patch, HBASE-21242.branch-2.002.patch, > HBASE-21242.branch-2.002.patch, HBASE-21242.branch-2.1.001.patch, > HBASE-21242.branch-2.1.001.patch, HBASE-21242.branch-2.1.001.patch, > HBASE-21242.branch-2.1.002.patch > > > Some minor fixups: > {code} > For RIT Duration, do better than print ms/seconds. Remove redundant UI > column dedicated to duration when we log it in the status field too. > Make bypass log at INFO level -- when DEBUG we can miss important > fixup detail like why we failed. > Make it so on complete of subprocedure, we note count of outstanding > siblings so we have a clue how much further the parent has to go before > it is done (Helpful when hundreds of servers doing SCP). > Have the SCP run the AP preflight check before creating an AP; saves > creation of hundreds of thousands of APs during fixup of this big cluster > of mine. > Don't log tablename three times when reporting remote call failed. > If lock is held already, note who has it. Also log after we get lock > or if we have to wait rather than log on entrance though we may > later have to wait (or we may have just picked up the lock). > {code} > Posting patch in a sec but let me try it on cluster too. -- This message was sent by Atlassian JIRA (v7.6.3#76005)