You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/13 16:52:00 UTC

[jira] [Resolved] (HBASE-6218) Add dynamic on/off tracing facility to regionserver; lightweight(?) record of read/write load

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

Andrew Kyle Purtell resolved HBASE-6218.
----------------------------------------
      Assignee:     (was: Michael Stack)
    Resolution: Incomplete

> 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: Michael Stack
>            Priority: Major
>
> 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
(v8.20.7#820007)