[
https://issues.apache.org/jira/browse/HBASE-23938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17107073#comment-17107073
]
Viraj Jasani commented on HBASE-23938:
--------------------------------------
HDFS maintenance might be an extra cost, rolling files, file size limit etc
should be handled manually. Whereas with system table, not only these factors
are taken care of but also we are not strictly dependent on HDFS FileSystem.
For HBase running in cloud, if HFiles are stored directly in S3, Azure Blob
storage etc, we would better want to store these logs there and we would prefer
HBase compute layer taking care of all HFile maintenance. That's the reason why
I also turned off WAL writes for this system table as per your suggestion to
not have multiple HDFS writes, which is quite valid. Thought?
> 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)
