[
https://issues.apache.org/jira/browse/HBASE-23938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105980#comment-17105980
]
Michael Stack commented on HBASE-23938:
---------------------------------------
Thanks for the pointer [~apurtell]
Not answered are in the parent:
* What will operator 'do' w/ the info. I can see querying ring buffer/table
content but interested in how it is used to change loadings; i'm sure there a
good use case. I ask because while a bunch of massive writes/reads might
provoke too slow, usually I see HDFS turn soggy because of rate rather than
particular reads/writes so interested in others findings. How do we know an
entry in the ring buffer is due to the explicit query rather than because of
surrounding read/writes. Is there a compelling case for recording in a table
perhaps built on findings so far from use of ring buffers frustrated some
because the history kept proved too short?
* Also unanswered is recording of environment at time of slow; state of
concurrent handler state, etc. (Perhaps external tooling for machine state and
perhaps hadoop+hbase metrics are sufficient?)
Just wondering about the benefit/rigging ratio. Thanks.
> Replicate slow/large RPC calls to HDFS
> --------------------------------------
>
> Key: HBASE-23938
> URL: https://issues.apache.org/jira/browse/HBASE-23938
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 3.0.0-alpha-1, 2.3.0, 1.7.0
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0
>
> Attachments: Screen Shot 2020-05-07 at 12.01.26 AM.png
>
>
> We should provide capability to replicate complete slow and large RPC logs to
> HDFS or create new system table in addition to Ring Buffer. This way we don't
> lose any of slow logs and operator can retrieve all the slow/large logs.
> Replicating logs to HDFS / creating new system table should be configurable.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
