You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hbase.apache.org by yuhang li <89...@gmail.com> on 2019/11/05 03:39:13 UTC
Region server web port doesn't respond
Hi all,
I'm using hbase 1.2.9.
Every time after starting regionserver several days, I cannot open its web
ui.
Using nc test tcp port, it's OK. But using curl, it just show 'curl: (52)
empty reply from server '.
Some abnormal message can be found in logs(in every minute):
2019-11-04 20:01:54,099 INFO [738111983@qtp-732189840-1 - Acceptor0
SelectChannelConnector@0.0.0.0:26030] mortbay.log:
org.mortbay.io.nio.SelectorManager$SelectSet@59f478d5 JVM BUG(s) -
injecting delay58 times
2019-11-04 20:01:54,099 INFO [738111983@qtp-732189840-1 - Acceptor0
SelectChannelConnector@0.0.0.0:26030] mortbay.log:
org.mortbay.io.nio.SelectorManager$SelectSet@59f478d5 JVM BUG(s) -
recreating selector 58 times, canceled keys 928 times
Re: Region server web port doesn't respond
Posted by yuhang li <89...@gmail.com>.
openjdk version "1.8.0_171"
OpenJDK Runtime Environment (build 1.8.0_171-b10)
OpenJDK 64-Bit Server VM (build 25.171-b10, mixed mode)
Sean Busbey <bu...@apache.org> 于2019年11月6日周三 上午11:44写道：
> what's your specific JDK version. Capturing the output of "java
> -version" would be the easiest way to get an answer.
>
> On Tue, Nov 5, 2019 at 8:09 PM yuhang li <89...@gmail.com> wrote:
> >
> > My jdk version is 1.8.
> >
> > I checked the jetty code and found that jetty does some work for jvm bugs
> > in jdk1.6 and 1.7. But what I use is jdk 1.8. This should be a bug of
> jetty.
> >
> > The workearounds jetty takes is to check the time cost of JAVA NIO
> > selector's select operation, and thinks it's BUG appearing when the time
> > cost is too small. see
> https://wiki.eclipse.org/Jetty/Feature/JVM_NIO_Bug
> >
> > According to jetty code, some system property can be set to control the
> > behaviour of this workearound. I'v set
> > "-Dorg.mortbay.io.nio.JVMBUG_THRESHHOLD=2147483647
> > -Dorg.mortbay.io.nio.MONITOR_PERIOD=0", maybe it cound work.
>
Re: Region server web port doesn't respond
Posted by Sean Busbey <bu...@apache.org>.
what's your specific JDK version. Capturing the output of "java
-version" would be the easiest way to get an answer.
On Tue, Nov 5, 2019 at 8:09 PM yuhang li <89...@gmail.com> wrote:
>
> My jdk version is 1.8.
>
> I checked the jetty code and found that jetty does some work for jvm bugs
> in jdk1.6 and 1.7. But what I use is jdk 1.8. This should be a bug of jetty.
>
> The workearounds jetty takes is to check the time cost of JAVA NIO
> selector's select operation, and thinks it's BUG appearing when the time
> cost is too small. see https://wiki.eclipse.org/Jetty/Feature/JVM_NIO_Bug
>
> According to jetty code, some system property can be set to control the
> behaviour of this workearound. I'v set
> "-Dorg.mortbay.io.nio.JVMBUG_THRESHHOLD=2147483647
> -Dorg.mortbay.io.nio.MONITOR_PERIOD=0", maybe it cound work.
Re: Region server web port doesn't respond
Posted by yuhang li <89...@gmail.com>.
My jdk version is 1.8.
I checked the jetty code and found that jetty does some work for jvm bugs
in jdk1.6 and 1.7. But what I use is jdk 1.8. This should be a bug of jetty.
The workearounds jetty takes is to check the time cost of JAVA NIO
selector's select operation, and thinks it's BUG appearing when the time
cost is too small. see https://wiki.eclipse.org/Jetty/Feature/JVM_NIO_Bug
According to jetty code, some system property can be set to control the
behaviour of this workearound. I'v set
"-Dorg.mortbay.io.nio.JVMBUG_THRESHHOLD=2147483647
-Dorg.mortbay.io.nio.MONITOR_PERIOD=0", maybe it cound work.
Re: Region server web port doesn't respond
Posted by Sean Busbey <bu...@apache.org>.
What's your JDK version
On Mon, Nov 4, 2019, 21:39 yuhang li <89...@gmail.com> wrote:
> Hi all,
>
> I'm using hbase 1.2.9.
>
> Every time after starting regionserver several days, I cannot open its web
> ui.
>
> Using nc test tcp port, it's OK. But using curl, it just show 'curl: (52)
> empty reply from server '.
>
> Some abnormal message can be found in logs(in every minute):
>
> 2019-11-04 20:01:54,099 INFO [738111983@qtp-732189840-1 - Acceptor0
> SelectChannelConnector@0.0.0.0:26030] mortbay.log:
> org.mortbay.io.nio.SelectorManager$SelectSet@59f478d5 JVM BUG(s) -
> injecting delay58 times
> 2019-11-04 20:01:54,099 INFO [738111983@qtp-732189840-1 - Acceptor0
> SelectChannelConnector@0.0.0.0:26030] mortbay.log:
> org.mortbay.io.nio.SelectorManager$SelectSet@59f478d5 JVM BUG(s) -
> recreating selector 58 times, canceled keys 928 times
>