hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ryan rawson (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (HBASE-3032) Master - dont shut down cluster if you run into a fatal error
Date Wed, 22 Sep 2010 21:09:36 GMT

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

ryan rawson reassigned HBASE-3032:
----------------------------------

    Assignee: stack

> Master - dont shut down cluster if you run into a fatal error
> -------------------------------------------------------------
>
>                 Key: HBASE-3032
>                 URL: https://issues.apache.org/jira/browse/HBASE-3032
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.89.20100621
>            Reporter: ryan rawson
>            Assignee: stack
>            Priority: Blocker
>             Fix For: 0.90.0
>
>
> Saw this message:
> 2010-09-22 13:10:03,547 FATAL org.apache.hadoop.hbase.master.MetaScanner: Caught error.
Starting shutdown.
> java.lang.OutOfMemoryError: unable to create new native thread
>         at java.lang.Thread.start0(Native Method)
>         at java.lang.Thread.start(Thread.java:597)
>         at org.apache.hadoop.hbase.ipc.HBaseClient$Connection.setupIOstreams(HBaseClient.java:328)
>         at org.apache.hadoop.hbase.ipc.HBaseClient.getConnection(HBaseClient.java:857)
>         at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:725)
>         at org.apache.hadoop.hbase.ipc.HBaseRPC$Invoker.invoke(HBaseRPC.java:252)
>         at $Proxy1.openScanner(Unknown Source)
>         at org.apache.hadoop.hbase.master.BaseScanner.scanRegion(BaseScanner.java:182)
>         at org.apache.hadoop.hbase.master.MetaScanner.scanOneMetaRegion(MetaScanner.java:73)
>         at org.apache.hadoop.hbase.master.MetaScanner.maintenanceScan(MetaScanner.java:129)
>         at org.apache.hadoop.hbase.master.BaseScanner.chore(BaseScanner.java:156)
>         at org.apache.hadoop.hbase.Chore.run(Chore.java:68)
> At this point the regionservers were instructed to exit, which caused more problems than
if the master just terminated itself.  
> This would prevent a backup master from picking up since the cluster is terminating!

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


Mime
View raw message