You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/09/27 04:32:00 UTC

[jira] [Updated] (HBASE-21242) [amv2] Miscellaneous minor log and assign procedure create improvements

     [ https://issues.apache.org/jira/browse/HBASE-21242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-21242:
--------------------------
    Attachment: HBASE-21242.branch-2.1.001.patch

> [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: HBASE-21242.branch-2.1.001.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)