hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-15886) Master shutsdown after ~3 min when using Native libraries
Date Fri, 30 Jun 2017 05:35:00 GMT

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

stack updated HBASE-15886:
    Fix Version/s:     (was: 2.0.0)

> Master shutsdown after ~3 min when using Native libraries
> ---------------------------------------------------------
>                 Key: HBASE-15886
>                 URL: https://issues.apache.org/jira/browse/HBASE-15886
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 2.0.0
>         Environment: Linux (Fedora).  Hbase stand alone mode, as well as pseudo-distributed
>            Reporter: Justin Paschall
> Hbase master appears to shutdown after ~3 minutes when I set env variables tp include
the paths to Native libraries.   For the first 3 minutes operations are working correctly,
I can create and write to tables.   This only occurs when I set HADOOP_HOME and LD_LIBRARY
PATH - which I do for purpose of enabling SNAPPY compression.     I do not observe this problem
problem when I run without setting those native library paths.
> Notably, the system is running properly at first for the first ~3 minutes, I can create
and write to tables, until a crash invariably occurs.
> I'm using Master from github  as of commit:   084b036
> Running in stand-alone non-distributed mode, but also see this in psuedodistributed.
> In hbase-master log I am seeing:
> 2016-05-24 13:09:01,550 WARN  [ProcedureExecutor-1] balancer.BaseLoadBalancer: Wanted
to do round robin assignment but no servers to assign to
> 2016-05-24 13:09:01,550 INFO  [ProcedureExecutor-1] procedure.ServerCrashProcedure: Caught
java.io.IOException: Unable to determine a plan to assign region(s) during region assignment,
will retry

This message was sent by Atlassian JIRA

View raw message