You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2017/02/22 23:14:44 UTC

[jira] [Comment Edited] (HBASE-17428) Expand on shell commands for detailed insight

    [ https://issues.apache.org/jira/browse/HBASE-17428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879442#comment-15879442 ] 

Josh Elser edited comment on HBASE-17428 at 2/22/17 11:14 PM:
--------------------------------------------------------------

.003 Has some cleanup over 002 and adds a ruby test.

FYI [~tedyu]


was (Author: elserj):
.003 Has some cleanup over 002 and adds a ruby test.

> Expand on shell commands for detailed insight
> ---------------------------------------------
>
>                 Key: HBASE-17428
>                 URL: https://issues.apache.org/jira/browse/HBASE-17428
>             Project: HBase
>          Issue Type: Sub-task
>          Components: shell
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: HBASE-16961
>
>         Attachments: HBASE-17428.001.patch, HBASE-17428.002.patch, HBASE-17428.003.HBASE-16961.patch
>
>
> Was talking over how to build some tests with [~romil.choksi], and what kind of information we capture and expose via some more shell commands.
> * Current SpaceQuotaSnapshots that the Master sees
> * Current SpaceQuotaSnapshots that a RS sees (or all RSs)
> * Current SpaceViolationPolicyEnforcements that a RS has enabled
> We can build out on the {{status}} command, with some options for different levels of detail, perhaps. Shouldn't be too tricky -- we have the info, just need to wire up java API, RPC, and shell command.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)