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

stack edited comment on HBASE-19841 at 1/31/18 3:54 AM:
--------------------------------------------------------

Starts out with "java.lang.OutOfMemoryError: unable to create new native 
thread".. thereafter can't start minhbasecluster.

Its on node H0

Yetus limit is 
|3797 (vs. ulimit of 5000)|

I added ulmit -a and it dumps this:
{code:java}
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 386176
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 60000
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 10240
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited{code}

Two java proceses on the box at start time only. No Geode running that I can 
see.


was (Author: stack):
Starts out with "java.lang.OutOfMemoryError: unable to create new native 
thread".. thereafter can't start minhbasecluster.

Yetus limit is 
|3797 (vs. ulimit of 5000)|

I added ulmit -a and it dumps this:
{code:java}
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 386176
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 60000
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 10240
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited{code}

Two java proceses on the box at start time only. No Geode running that I can 
see.

> Tests against hadoop3 fail with StreamLacksCapabilityException
> --------------------------------------------------------------
>
>                 Key: HBASE-19841
>                 URL: https://issues.apache.org/jira/browse/HBASE-19841
>             Project: HBase
>          Issue Type: Test
>            Reporter: Ted Yu
>            Assignee: Mike Drob
>            Priority: Major
>             Fix For: 2.0.0-beta-2
>
>         Attachments: 19841.007.patch, 19841.06.patch, 19841.v0.txt, 
> 19841.v1.txt, HBASE-19841.v10.patch, HBASE-19841.v11.patch, 
> HBASE-19841.v2.patch, HBASE-19841.v3.patch, HBASE-19841.v4.patch, 
> HBASE-19841.v5.patch, HBASE-19841.v7.patch, HBASE-19841.v8.patch, 
> HBASE-19841.v8.patch, HBASE-19841.v8.patch, HBASE-19841.v9.patch
>
>
> The following can be observed running against hadoop3:
> {code}
> java.io.IOException: cannot get log writer
>       at 
> org.apache.hadoop.hbase.regionserver.TestCompactingMemStore.compactingSetUp(TestCompactingMemStore.java:107)
>       at 
> org.apache.hadoop.hbase.regionserver.TestCompactingMemStore.setUp(TestCompactingMemStore.java:89)
> Caused by: 
> org.apache.hadoop.hbase.util.CommonFSUtils$StreamLacksCapabilityException: 
> hflush and hsync
>       at 
> org.apache.hadoop.hbase.regionserver.TestCompactingMemStore.compactingSetUp(TestCompactingMemStore.java:107)
>       at 
> org.apache.hadoop.hbase.regionserver.TestCompactingMemStore.setUp(TestCompactingMemStore.java:89)
> {code}
> This was due to hbase-server/src/test/resources/hbase-site.xml not being 
> picked up by Configuration object. Among the configs from this file, the 
> value for "hbase.unsafe.stream.capability.enforce" relaxes check for presence 
> of hflush and hsync. Without this config entry,  
> StreamLacksCapabilityException is thrown.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to