You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2010/01/04 05:20:55 UTC
[jira] Created: (HBASE-2088) Review code base to purge wacky things
done to compensate for lack of hdfs sync
Review code base to purge wacky things done to compensate for lack of hdfs sync
-------------------------------------------------------------------------------
Key: HBASE-2088
URL: https://issues.apache.org/jira/browse/HBASE-2088
Project: Hadoop HBase
Issue Type: Task
Reporter: stack
"Like we did with the compaction limiting thread and region server "safe mode" after the transition to 0.20." apurtell
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-2088) Review code base to purge wacky
things done to compensate for lack of hdfs sync
Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796074#action_12796074 ]
Jean-Daniel Cryans commented on HBASE-2088:
-------------------------------------------
We don't flush catalog table at 1M anymore in trunk, I removed it.
We do force roll of the latest WAL file every hour. I think it's kinda nice to flush very old stuff, we could set it higher.
> Review code base to purge wacky things done to compensate for lack of hdfs sync
> -------------------------------------------------------------------------------
>
> Key: HBASE-2088
> URL: https://issues.apache.org/jira/browse/HBASE-2088
> Project: Hadoop HBase
> Issue Type: Task
> Reporter: stack
>
> "Like we did with the compaction limiting thread and region server "safe mode" after the transition to 0.20." apurtell
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-2088) Review code base to purge wacky
things done to compensate for lack of hdfs sync
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796072#action_12796072 ]
stack commented on HBASE-2088:
------------------------------
Look at WAL log sizes. We were careful making sure we rotated frequently at < hdfs block size. Is this still needed?
We also did stuff like flush catalog tables at 1M or so. Do we still do this?
> Review code base to purge wacky things done to compensate for lack of hdfs sync
> -------------------------------------------------------------------------------
>
> Key: HBASE-2088
> URL: https://issues.apache.org/jira/browse/HBASE-2088
> Project: Hadoop HBase
> Issue Type: Task
> Reporter: stack
>
> "Like we did with the compaction limiting thread and region server "safe mode" after the transition to 0.20." apurtell
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.