[
https://issues.apache.org/jira/browse/HBASE-5262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192603#comment-13192603
]
stack commented on HBASE-5262:
------------------------------
@Mikhail We used have an extra column family in .META. called history. Into it
we'd write 'events'. It was stripped because though a nice idea, it caused
more trouble than it was worth (x-cluster deadlocking, interfering w/
shutdowns, growing at a different rate to the info family in .META.)...so yeah,
should fail fast if can't put events, etc.
> 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
