[
https://issues.apache.org/jira/browse/HBASE-5262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192500#comment-13192500
]
Todd Lipcon commented on HBASE-5262:
------------------------------------
Also we should isolate the writing of this table to a separate thread with a
bounded queue (which drops off the end if it becomes full). Otherwise we may
run into issues where the logging of information may actually cause operations
to fail, or cause deadlocks, etc. (eg a write to a region causes a flush which
causes a write to the eventlog table on the same server, but all of the IPC
threads are blocked because of the ongoing flush, so the eventlog write never
completes). So, we should always assume that the information in the event log
is potentially lossy, and only use it for heuristics and diagnosis, not for
anything critical to operation.
> 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
