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 2009/01/18 00:08:59 UTC

[jira] Resolved: (HBASE-774) Optional flush provokes periodic large spike in cluster traffic

     [ https://issues.apache.org/jira/browse/HBASE-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-774.
-------------------------

    Resolution: Invalid

We don't have optional flush any more so resolving invalid though we may see a different manifestation when major compactions run once a day.

> Optional flush provokes periodic large spike in cluster traffic
> ---------------------------------------------------------------
>
>                 Key: HBASE-774
>                 URL: https://issues.apache.org/jira/browse/HBASE-774
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>            Priority: Critical
>         Attachments: network.gif
>
>
> Looking at our 70-node cluster, whose current state is mostly read-only but for a service that is trickling in pages at about 5/600 an hour, network traffic goes through the roof every 30 minutes.  This is 0.1.3.  Regionserver logs are silent but for the optional flush that runs every 30 minutes.  The optional flush will put a few small files out on the filesystem tripping compactions of small files.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.