[
https://issues.apache.org/jira/browse/HBASE-5262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192179#comment-13192179
]
Mikhail Bautin commented on HBASE-5262:
---------------------------------------
I was thinking of a lightly-loaded system table different from .META.. This way
it is easier to control this feature, and we can even make it optional based on
the configuration. Storing event log data in HBase makes sense to me because we
don't expect a huge number of records compared to the user's data itself, and
we probably don't want to implement another logging framework with HDFS file
management, cleaning up old files, etc. The multiple writers to one file
question is also there. If we store this data in HBase, then yes, we can use
TTL to set event log retention to e.g. one month or so, or make it configurable.
> Structured event log for HBase for monitoring and auto-tuning performance
> -------------------------------------------------------------------------
>
> Key: HBASE-5262
> URL: https://issues.apache.org/jira/browse/HBASE-5262
> Project: HBase
> Issue Type: Improvement
> Reporter: Mikhail Bautin
>
> Creating this JIRA to open a discussion about a structured (machine-readable)
> log that will record events such as compaction start/end times, compaction
> input/output files, their sizes, the same for flushes, etc. This can be
> stored e.g. in a new system table in HBase itself. The data from this log can
> then be analyzed and used to optimize compactions at run time, or otherwise
> auto-tune HBase configuration to reduce the number of knobs the user has to
> configure.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
