You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Anoop Sam John (JIRA)" <ji...@apache.org> on 2018/06/07 06:42:00 UTC
[jira] [Commented] (HBASE-20483) [PERFORMANCE] Flushing is 2x
slower in hbase2.
[ https://issues.apache.org/jira/browse/HBASE-20483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16504311#comment-16504311 ]
Anoop Sam John commented on HBASE-20483:
----------------------------------------
[~stack] The other jira abt SegmentScanner fixed this also right?
> [PERFORMANCE] Flushing is 2x slower in hbase2.
> ----------------------------------------------
>
> Key: HBASE-20483
> URL: https://issues.apache.org/jira/browse/HBASE-20483
> Project: HBase
> Issue Type: Sub-task
> Components: Performance
> Reporter: stack
> Assignee: stack
> Priority: Major
> Attachments: 0001-HBASE-20483-perpertual-flush-and-memstore-fill-branch-2.0.patch, 0001-HBASE-20483-perpetual-flush.branch-1.4.patch, 0001-HBASE-20483-perpetual-flush.branch-1.4.patch, 0001-HBASE-20483-perpetual.tests.patch, 0001-HBASE-20483-perpetual.tests.patch, 0001-Perpetual-flush-memstore-fill-etc.-tools.patch, PerpetualFlushingProgram.patch, PerpetualFlushingProgram1.2.patch, SnapshotSegmentScanner_2.0.0.patch
>
>
> When flush is slow, memstores backup and go slower. See "1.2.7 vs. 2.0.0 Flush History" https://docs.google.com/spreadsheets/d/1sihTxb4aCplR3Rr_GGXkPlwhMIm-CbB9j_5339AS0Zc/edit#gid=1016758826 for compare. First noted by [~anoop.hbase]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)