You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2012/11/06 06:48:14 UTC

[jira] [Updated] (HBASE-6853) IllegalArgumentException is thrown when an empty region is splitted

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

Ted Yu updated HBASE-6853:
--------------------------

    Summary: IllegalArgumentException is thrown when an empty region is splitted  (was: IllegalArgument Exception is thrown when an empty region is spliitted.)
    
> IllegalArgumentException is thrown when an empty region is splitted
> -------------------------------------------------------------------
>
>                 Key: HBASE-6853
>                 URL: https://issues.apache.org/jira/browse/HBASE-6853
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.92.1, 0.94.1
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: Priyadarshini
>             Fix For: 0.94.2, 0.96.0
>
>         Attachments: HBASE-6853_0.94, HBASE-6853_2_splitsuccess.patch, HBASE-6853_addendum.patch, HBASE-6853.patch, HBASE-6853_splitfailure.patch
>
>
> This is w.r.t a mail sent in the dev mail list.
> Empty region split should be handled gracefully.  Either we should not allow the split to happen if we know that the region is empty or we should allow the split to happen by setting the no of threads to the thread pool executor as 1.
> {code}
> int nbFiles = hstoreFilesToSplit.size();
> ThreadFactoryBuilder builder = new ThreadFactoryBuilder();
>     builder.setNameFormat("StoreFileSplitter-%1$d");
>     ThreadFactory factory = builder.build();
>     ThreadPoolExecutor threadPool =
>       (ThreadPoolExecutor) Executors.newFixedThreadPool(nbFiles, factory);
>     List<Future<Void>> futures = new ArrayList<Future<Void>>(nbFiles);
> {code}
> Here the nbFiles needs to be a non zero positive value.
>  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira