hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HBASE-10324) refactor deferred-log-flush/Durability related interface/code/naming to align with changed semantic of the new write thread model
Date Mon, 13 Jan 2014 18:10:53 GMT

    [ https://issues.apache.org/jira/browse/HBASE-10324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13869773#comment-13869773
] 

Andrew Purtell edited comment on HBASE-10324 at 1/13/14 6:10 PM:
-----------------------------------------------------------------

Nit: Remove the '@Deprecated' tags from the renamed methods. The deprecated methods have been
effectively removed and replaced with a new API.
Edit: Committer, please also insure the deprecated methods appear as such in 0.96 branch.


was (Author: apurtell):
Nit: Remove the '@Deprecated' tags from the renamed methods. The deprecated methods have been
effectively removed and replaced with a new API.

> refactor deferred-log-flush/Durability related interface/code/naming to align with changed
semantic of the new write thread model
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-10324
>                 URL: https://issues.apache.org/jira/browse/HBASE-10324
>             Project: HBase
>          Issue Type: Improvement
>          Components: Client, regionserver
>            Reporter: Feng Honghua
>            Assignee: Feng Honghua
>         Attachments: HBASE-10324-trunk_v0.patch, HBASE-10324-trunk_v1.patch, HBASE-10324-trunk_v2.patch
>
>
> By the new write thread model introduced by [HBASE-8755|https://issues.apache.org/jira/browse/HBASE-8755],
some deferred-log-flush/Durability API/code/names should be change accordingly:
> 1. no timer-triggered deferred-log-flush since flush is always done by async threads,
so configuration 'hbase.regionserver.optionallogflushinterval' is no longer needed
> 2. the async writer-syncer-notifier threads will always be triggered implicitly, this
semantic is that it always holds that 'hbase.regionserver.optionallogflushinterval' > 0,
so deferredLogSyncDisabled in HRegion.java which affects durability behavior should always
be false
> 3. what HTableDescriptor.isDeferredLogFlush really means is the write  can return without
waiting for the sync is done, so the interface name should be changed to isAsyncLogFlush/setAsyncLogFlush
to reflect their real meaning



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message