<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<configuration>
  <property>
    <name>hbase.zookeeper.quorum</name>
    <value>...</value>
  </property>
  <property>
    <name>zookeeper.znode.parent</name>
    <value>/hbase</value>
  </property>
  <property>
    <name>hbase.zookeeper.property.dataDir</name>
    <value>/disk0/zk/data</value>
  </property>
  <property>
    <name>hbase.rootdir</name>
    <value>hdfs://master52.hadoop.prod.kontagent.com:8020/hbase</value>
  </property>
  <property>
    <name>hbase.cluster.distributed</name>
    <value>true</value>
  </property>
  <property>
    <name>hbase.hregion.max.filesize</name>
    <value>10737418240</value>
  </property>
  <property>
    <name>hbase.regionserver.lease.period</name>
    <value>900000</value> <!-- 15 minutes -->
  </property>
  <property>
    <name>hbase.rpc.timeout</name>
    <value>900000</value> <!-- 15 minutes -->
  </property>

  <property>
    <name>zookeeper.session.timeout</name>
    <value>120000</value> <!-- 2 mins -->
  </property>
  <property>
    <name>hbase.zookeeper.property.tickTime</name>
    <value>2000</value> <!-- matches zoo.cfg -->
  </property>

  <property>
    <name>hbase.snapshot.enabled</name>
    <value>true</value>
  </property>

  <property>
     <name>hbase.hregion.majorcompaction</name>
     <value>0</value>
  </property>

  <!--
      Added this setting in response to "RegionServerTooBusy" exceptions that we were seeing on tesseract. The regionservers weren't able to flush due to too many storefiles (this setting), causing the memstores to fill up, and the region to be unable to write. Bumping
this setting relaxes that requirement slightly, allowing us to keep writing to the affected regions. Longer term fix would be to
do a better job of preventing region hotspotting, such that no region has too high a writeload.
-->
  <property>
    <name>hbase.hstore.blockingStoreFiles</name>
    <value>20</value>
  </property>


<!--

Increasing this so that we create larger HFiles and not flushs often hence improving write perf.

 Memstore will be flushed to disk if size of the memstore
 exceeds this number of bytes. Value is checked by a thread that runs
 every hbase.server.thread.wakefrequency.
-->
<property>
 <name>hbase.hregion.memstore.flush.size</name>
 <value>536870912</value>
</property>
</configuration>