Subject: [jira] Created: (HBASE-1801) Tool to clean regions on DFS - msg#00429

Previous Message by Date: click to view message preview

[jira] Updated: (HBASE-1800) Too many ZK connections

[ https://issues.apache.org/jira/browse/HBASE-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-1800: ---------------------------------- Fix Version/s: (was: 0.20.1) 0.20.0 Let's pull this in to 0.20 also. New users who set up single node ZK installs will hit this. > Too many ZK connections > ----------------------- > > Key: HBASE-1800 > URL: https://issues.apache.org/jira/browse/HBASE-1800 > Project: Hadoop HBase > Issue Type: Improvement > Reporter: Jean-Daniel Cryans > Fix For: 0.20.0, 0.21.0 > > Attachments: HBASE-1800-v1.patch > > > Currently we open tons of new connections to Zookeeper, like every time we > instantiate a new HTable. There is a maximum number of client connections as > described here: > {code} > <property> > <name>hbase.zookeeper.property.maxClientCnxns</name> > <value>30</value> > <description>Property from ZooKeeper's config zoo.cfg. > Limit on number of concurrent connections (at the socket level) that a > single client, identified by IP address, may make to a single member of > the ZooKeeper ensemble. Set high to avoid zk connection issues running > standalone and pseudo-distributed. > </description> > </property> > {code} > If you hit that max number, ZK will just refuse your connections. Suppose you > have 4 maps running on a server hosting a RS, you may actually lose your > connection in the RS and eventually hit a session timeout. Maybe we should > singleton ZKW? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.

Next Message by Date: click to view message preview

[jira] Updated: (HBASE-1801) Tool to clean regions on DFS

[ https://issues.apache.org/jira/browse/HBASE-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Daniel Cryans updated HBASE-1801: -------------------------------------- Attachment: clean_table.rb Little tool inspired by copy_table.rb > Tool to clean regions on DFS > ---------------------------- > > Key: HBASE-1801 > URL: https://issues.apache.org/jira/browse/HBASE-1801 > Project: Hadoop HBase > Issue Type: Bug > Affects Versions: 0.19.3 > Reporter: Jean-Daniel Cryans > Attachments: clean_table.rb > > > If you have a cluster running for some time, you probably have more regions > on DFS than in META. Here is a tool to remove them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.

Previous Message by Thread: click to view message preview

[jira] Created: (HBASE-1803) cant set hbase.regionserver.optionallogflushinterval < hbase.server.thread.wakefrequency

cant set hbase.regionserver.optionallogflushinterval < hbase.server.thread.wakefrequency ---------------------------------------------------------------------------------------- Key: HBASE-1803 URL: https://issues.apache.org/jira/browse/HBASE-1803 Project: Hadoop HBase Issue Type: Bug Affects Versions: 0.20.0 Reporter: ryan rawson Fix For: 0.20.1, 0.21.0 this is a problem because we'd like to, for example, flush edits every second, yet we dont want to run all threads at a 10s interval (eg: lease checking, etc) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.

Next Message by Thread: click to view message preview

[jira] Updated: (HBASE-1801) Tool to clean regions on DFS

[ https://issues.apache.org/jira/browse/HBASE-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Daniel Cryans updated HBASE-1801: -------------------------------------- Attachment: clean_table.rb Little tool inspired by copy_table.rb > Tool to clean regions on DFS > ---------------------------- > > Key: HBASE-1801 > URL: https://issues.apache.org/jira/browse/HBASE-1801 > Project: Hadoop HBase > Issue Type: Bug > Affects Versions: 0.19.3 > Reporter: Jean-Daniel Cryans > Attachments: clean_table.rb > > > If you have a cluster running for some time, you probably have more regions > on DFS than in META. Here is a tool to remove them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.