[ https://issues.apache.org/jira/browse/HBASE-24718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162171#comment-17162171 ]
Nick Dimiduk commented on HBASE-24718: -------------------------------------- I had a chat with [~vjasani] on Slack about this patch, bringing the conclusion here. I asked that this not be back-ported to branch-2.3 unless it proves necessary for some critical bug fixes. As there are no known bugs as of now, better to leave it at branch-2. > Generic NamedQueue framework for recent in-memory history (refactor slowlog) > ---------------------------------------------------------------------------- > > Key: HBASE-24718 > URL: https://issues.apache.org/jira/browse/HBASE-24718 > Project: HBase > Issue Type: Sub-task > Reporter: Viraj Jasani > Assignee: Viraj Jasani > Priority: Major > Fix For: 3.0.0-alpha-1, 2.4.0 > > Attachments: Screen Shot 2020-07-20 at 2.50.34 PM.png > > > As per the discussion on parent jira, we should come up with named queue > (online ring buffer) to serve recent history for multiple use-cases like > slowlog, balancer decision, other region activities e.g flush, compaction, > split, merge etc. > Since we already have slow/large rpc logs in ring buffer (HBASE-22978), as > part of this Jira, the proposal is to refactor slowlog provider to get > generic payload for ring buffer and based on event type (slow_log is the only > one for now), we can have separate internal in-memory queues. > After this refactor, it should be relatively simpler to use the same > framework and create more cases like parent Jira (balancer decision in ring > buffer). -- This message was sent by Atlassian Jira (v8.3.4#803005)