The specified interval (which should be between 0.0 and 1.0) Split the call queues into read and write queues. handler.factorįactor to determine the number of call queues.Ī value of 0 means a single queue shared between all the handlers.Ī value of 1 means that each handler has its own queue. Start with twice the CPU count and tune from there. If mostly read-only, handlers count close to cpu countĭoes well. Too many handlers can be counter-productive. Same property is used by the Master for count of master handlers. Useful for testing, turned off by default.Ĭount of RPC Listener instances spun up on RegionServers. Whether or not the Master or RegionServer The address for the HBase RegionServer web UI Set to -1 if you do not want the RegionServer UI to run. The port for the HBase RegionServer web UI The port the HBase RegionServer binds to. Split is now run master-side hence the rename (If a Splitting a region, how long to wait on the file-splitting Sense when Master is serving Regions (not the default). UI server shared by the Master and RegionServer. UI port () and redirects requests to the web Whether or not the Master listens to the Master web Always add the aboveĭefault hfile cleaners in the list as they will be overwritten in Implement your own BaseHFileCleanerDelegate, just put it in HBase's classpathĪnd add the fully qualified class name here. So put the cleaner that prunes the most files in front.

These HFiles cleaners are called in order, Ī comma-separated list of BaseHFileCleanerDelegate invoked by To whatever $/oldWALs) directory,Īfter which it will be cleaned by a Master thread. Running at on port 9000, set this value to: HDFS directory '/hbase' where the HDFS instance's namenode is The directory shared by region servers and into '/tmp' directory is cleared on machine restart. Than '/tmp', the usual resolve for java.io.tmpdir, as the Temporary directory on the local filesystem.Ĭhange this setting to point to a location more permanent

Hbase archive cleaner