hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-6218) Add dynamic on/off tracing facility to regionserver; lightweight(?) record of read/write load
Date Tue, 26 Sep 2017 21:36:00 GMT

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

Mike Drob updated HBASE-6218:
-----------------------------
    Status: In Progress  (was: Patch Available)

No patch attached, kicking out of patch available.

> Add dynamic on/off tracing facility to regionserver; lightweight(?) record of read/write
load
> ---------------------------------------------------------------------------------------------
>
>                 Key: HBASE-6218
>                 URL: https://issues.apache.org/jira/browse/HBASE-6218
>             Project: HBase
>          Issue Type: New Feature
>          Components: test
>            Reporter: stack
>            Assignee: stack
>
> It'd be sweet if we could kick a regionserver and have it start recording the read/write
load.  Then after we'd taken a sample, we could turn off the recording.
> Chatting at the meetup today, replaying the WALs would give you the write side (though
missing would be the rate at which the client should play the edits -- perhaps we could add
this to the WALEdit if its not already there?).
> Read side we'd need something new recording the read load (Perhaps we'd have a single
trace for read and write but somehow you could get the write from the WAL logs).  It would
be nice too if we could verify that we read the right thing somehow (hash of the return when
the trace switch is thrown?  Would need to cater to differences in timestamp possibly?)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message