Want more features on Pastebin? Sign Up, it's FREE!
Guest

Untitled

By: a guest on Apr 7th, 2011  |  syntax: None  |  size: 23.13 KB  |  views: 70  |  expires: Never
download  |  raw  |  embed  |  report abuse  |  print
Text below is selected. Please press Ctrl+C to copy to your clipboard. (⌘+C on Mac)
  1. <?xml version="1.0"?>
  2. <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
  3. <!--
  4. /**
  5.  * Copyright 2009 The Apache Software Foundation
  6.  *
  7.  * Licensed to the Apache Software Foundation (ASF) under one
  8.  * or more contributor license agreements.  See the NOTICE file
  9.  * distributed with this work for additional information
  10.  * regarding copyright ownership.  The ASF licenses this file
  11.  * to you under the Apache License, Version 2.0 (the
  12.  * "License"); you may not use this file except in compliance
  13.  * with the License.  You may obtain a copy of the License at
  14.  *
  15.  *     http://www.apache.org/licenses/LICENSE-2.0
  16.  *
  17.  * Unless required by applicable law or agreed to in writing, software
  18.  * distributed under the License is distributed on an "AS IS" BASIS,
  19.  * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  20.  * See the License for the specific language governing permissions and
  21.  * limitations under the License.
  22.  */
  23. -->
  24. <configuration>
  25.   <property>
  26.     <name>hbase.rootdir</name>
  27.     <value>file:///tmp/hbase-${user.name}/hbase</value>
  28.     <description>The directory shared by region servers.
  29.     Should be fully-qualified to include the filesystem to use.
  30.     E.g: hdfs://NAMENODE_SERVER:PORT/HBASE_ROOTDIR
  31.     </description>
  32.   </property>
  33.   <property>
  34.     <name>hbase.master.port</name>
  35.     <value>60000</value>
  36.     <description>The port master should bind to.</description>
  37.   </property>
  38.   <property>
  39.     <name>hbase.cluster.distributed</name>
  40.     <value>false</value>
  41.     <description>The mode the cluster will be in. Possible values are
  42.       false: standalone and pseudo-distributed setups with managed Zookeeper
  43.       true: fully-distributed with unmanaged Zookeeper Quorum (see hbase-env.sh)
  44.     </description>
  45.   </property>
  46.   <property>
  47.     <name>hbase.tmp.dir</name>
  48.     <value>/tmp/hbase-${user.name}</value>
  49.     <description>Temporary directory on the local filesystem.</description>
  50.   </property>
  51.   <property>
  52.     <name>hbase.master.info.port</name>
  53.     <value>60010</value>
  54.     <description>The port for the hbase master web UI
  55.     Set to -1 if you do not want the info server to run.
  56.     </description>
  57.   </property>
  58.   <property>
  59.     <name>hbase.master.info.bindAddress</name>
  60.     <value>0.0.0.0</value>
  61.     <description>The address for the hbase master web UI
  62.     </description>
  63.   </property>
  64.   <property>
  65.     <name>hbase.client.write.buffer</name>
  66.     <value>2097152</value>
  67.     <description>Size of the write buffer in bytes. A bigger buffer takes more
  68.     memory -- on both the client and server side since server instantiates
  69.     the passed write buffer to process it -- but reduces the number of RPC.
  70.     For an estimate of server-side memory-used, evaluate
  71.     hbase.client.write.buffer * hbase.regionserver.handler.count
  72.     </description>
  73.   </property>
  74.   <property>
  75.     <name>hbase.master.meta.thread.rescanfrequency</name>
  76.     <value>60000</value>
  77.     <description>How long the HMaster sleeps (in milliseconds) between scans of
  78.     the root and meta tables.
  79.     </description>
  80.   </property>
  81.   <property>
  82.     <name>hbase.regionserver.port</name>
  83.     <value>60020</value>
  84.     <description>The port an HBase region server binds to.
  85.     </description>
  86.   </property>
  87.   <property>
  88.     <name>hbase.regionserver.info.port</name>
  89.     <value>60030</value>
  90.     <description>The port for the hbase regionserver web UI
  91.     Set to -1 if you do not want the info server to run.
  92.     </description>
  93.   </property>
  94.   <property>
  95.     <name>hbase.regionserver.info.port.auto</name>
  96.     <value>false</value>
  97.     <description>Info server auto port bind. Enables automatic port
  98.     search if hbase.regionserver.info.port is already in use.
  99.     Useful for testing, turned off by default.
  100.     </description>
  101.   </property>
  102.   <property>
  103.     <name>hbase.regionserver.info.bindAddress</name>
  104.     <value>0.0.0.0</value>
  105.     <description>The address for the hbase regionserver web UI
  106.     </description>
  107.   </property>
  108.   <property>
  109.     <name>hbase.regionserver.class</name>
  110.     <value>org.apache.hadoop.hbase.ipc.HRegionInterface</value>
  111.     <description>An interface that is assignable to HRegionInterface.  Used in HClient for
  112.     opening proxy to remote region server.
  113.     </description>
  114.   </property>
  115.   <property>
  116.     <name>hbase.client.pause</name>
  117.     <value>1000</value>
  118.     <description>General client pause value.  Used mostly as value to wait
  119.     before running a retry of a failed get, region lookup, etc.</description>
  120.   </property>
  121.   <property>
  122.     <name>hbase.client.retries.number</name>
  123.     <value>10</value>
  124.     <description>Maximum retries.  Used as maximum for all retryable
  125.     operations such as fetching of the root region from root region
  126.     server, getting a cell's value, starting a row update, etc.
  127.     Default: 10.
  128.     </description>
  129.   </property>
  130.   <property>
  131.     <name>hbase.client.scanner.caching</name>
  132.     <value>1</value>
  133.     <description>Number of rows that will be fetched when calling next
  134.     on a scanner if it is not served from memory. Higher caching values
  135.     will enable faster scanners but will eat up more memory and some
  136.     calls of next may take longer and longer times when the cache is empty.
  137.     </description>
  138.   </property>
  139.   <property>
  140.     <name>hbase.client.keyvalue.maxsize</name>
  141.     <value>10485760</value>
  142.     <description>Specifies the combined maximum allowed size of a KeyValue
  143.     instance. This is to set an upper boundary for a single entry saved in a
  144.     storage file. Since they cannot be split it helps avoiding that a region
  145.     cannot be split any further because the data is too large. It seems wise
  146.     to set this to a fraction of the maximum region size. Setting it to zero
  147.     or less disables the check.
  148.     </description>
  149.   </property>
  150.   <property>
  151.     <name>hbase.regionserver.lease.period</name>
  152.     <value>60000</value>
  153.     <description>HRegion server lease period in milliseconds. Default is
  154.     60 seconds. Clients must report in within this period else they are
  155.     considered dead.</description>
  156.   </property>
  157.   <property>
  158.     <name>hbase.regionserver.handler.count</name>
  159.     <value>25</value>
  160.     <description>Count of RPC Server instances spun up on RegionServers
  161.     Same property is used by the HMaster for count of master handlers.
  162.     Default is 25.
  163.     </description>
  164.   </property>
  165.   <property>
  166.     <name>hbase.regionserver.msginterval</name>
  167.     <value>1000</value>
  168.     <description>Interval between messages from the RegionServer to HMaster
  169.     in milliseconds. Use a high value like 3000 for clusters with more than 10
  170.     nodes. Default is 1 second so that HBase seems more 'live'.
  171.     </description>
  172.   </property>
  173.   <property>
  174.     <name>hbase.regionserver.flushlogentries</name>
  175.     <value>1</value>
  176.     <description>Sync the HLog to the HDFS when it has accumulated this many
  177.     entries. Default 1. Value is checked on every HLog.hflush
  178.     </description>
  179.   </property>
  180.   <property>
  181.     <name>hbase.regionserver.optionallogflushinterval</name>
  182.     <value>1000</value>
  183.     <description>Sync the HLog to the HDFS after this interval if it has not
  184.     accumulated enough entries to trigger a sync. Default 1 second. Units:
  185.     milliseconds.
  186.     </description>
  187.   </property>
  188.   <property>
  189.     <name>hbase.regionserver.regionSplitLimit</name>
  190.     <value>2147483647</value>
  191.     <description>Limit for the number of regions after which no more region
  192.     splitting should take place. This is not a hard limit for the number of
  193.     regions but acts as a guideline for the regionserver to stop splitting after
  194.     a certain limit. Default is set to MAX_INT.
  195.     </description>
  196.   </property>
  197.   <property>
  198.     <name>hbase.regionserver.logroll.period</name>
  199.     <value>3600000</value>
  200.     <description>Period at which we will roll the commit log.</description>
  201.   </property>
  202.   <property>
  203.     <name>hbase.regionserver.hlog.reader.impl</name>
  204.     <value>org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader</value>
  205.     <description>The HLog file reader implementation.</description>
  206.   </property>
  207.   <property>
  208.     <name>hbase.regionserver.hlog.writer.impl</name>
  209.     <value>org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogWriter</value>
  210.     <description>The HLog file writer implementation.</description>
  211.   </property>
  212.   <property>
  213.     <name>hbase.regionserver.thread.splitcompactcheckfrequency</name>
  214.     <value>20000</value>
  215.     <description>How often a region server runs the split/compaction check.
  216.     </description>
  217.   </property>
  218.   <property>
  219.     <name>hbase.regionserver.nbreservationblocks</name>
  220.     <value>4</value>
  221.     <description>The number of reservation blocks which are used to prevent
  222.     unstable region servers caused by an OOME.
  223.     </description>
  224.   </property>
  225.   <property>
  226.     <name>hbase.zookeeper.dns.interface</name>
  227.     <value>default</value>
  228.     <description>The name of the Network Interface from which a ZooKeeper server
  229.       should report its IP address.
  230.     </description>
  231.   </property>
  232.   <property>
  233.     <name>hbase.zookeeper.dns.nameserver</name>
  234.     <value>default</value>
  235.     <description>The host name or IP address of the name server (DNS)
  236.       which a ZooKeeper server should use to determine the host name used by the
  237.       master for communication and display purposes.
  238.     </description>
  239.   </property>
  240.   <property>
  241.     <name>hbase.regionserver.dns.interface</name>
  242.     <value>default</value>
  243.     <description>The name of the Network Interface from which a region server
  244.       should report its IP address.
  245.     </description>
  246.   </property>
  247.   <property>
  248.     <name>hbase.regionserver.dns.nameserver</name>
  249.     <value>default</value>
  250.     <description>The host name or IP address of the name server (DNS)
  251.       which a region server should use to determine the host name used by the
  252.       master for communication and display purposes.
  253.     </description>
  254.   </property>
  255.   <property>
  256.     <name>hbase.master.dns.interface</name>
  257.     <value>default</value>
  258.     <description>The name of the Network Interface from which a master
  259.       should report its IP address.
  260.     </description>
  261.   </property>
  262.   <property>
  263.     <name>hbase.master.dns.nameserver</name>
  264.     <value>default</value>
  265.     <description>The host name or IP address of the name server (DNS)
  266.       which a master should use to determine the host name used
  267.       for communication and display purposes.
  268.     </description>
  269.   </property>
  270.   <property>
  271.     <name>hbase.regionserver.global.memstore.upperLimit</name>
  272.     <value>0.4</value>
  273.     <description>Maximum size of all memstores in a region server before new
  274.       updates are blocked and flushes are forced. Defaults to 40% of heap
  275.     </description>
  276.   </property>
  277.   <property>
  278.     <name>hbase.regionserver.global.memstore.lowerLimit</name>
  279.     <value>0.35</value>
  280.     <description>When memstores are being forced to flush to make room in
  281.       memory, keep flushing until we hit this mark. Defaults to 30% of heap.
  282.       This value equal to hbase.regionserver.global.memstore.upperLimit causes
  283.       the minimum possible flushing to occur when updates are blocked due to
  284.       memstore limiting.
  285.     </description>
  286.   </property>
  287.   <property>
  288.     <name>hbase.hbasemaster.maxregionopen</name>
  289.     <value>120000</value>
  290.     <description>Period to wait for a region open.  If regionserver
  291.     takes longer than this interval, assign to a new regionserver.
  292.     </description>
  293.   </property>
  294.   <property>
  295.     <name>hbase.master.logcleaner.ttl</name>
  296.     <value>600000</value>
  297.     <description>Maximum time a log can stay in the .oldlogdir directory,
  298.     after which it will be cleaned by a master thread.
  299.     </description>
  300.   </property>
  301.   <property>
  302.     <name>hbase.master.logcleaner.plugins</name>
  303.     <value>org.apache.hadoop.hbase.master.TimeToLiveLogCleaner,org.apache.hadoop.hbase.replication.master.ReplicationLogCleaner</value>
  304.     <description>A comma-separated list of LogCleanerDelegate that are used
  305.     in LogsCleaner. These log cleaners are called in order, so put the log
  306.     cleaner that prunes the most log files in the front. To implement your own
  307.     LogCleanerDelegate, just put it in HBase's classpath and add the fully
  308.     qualified class name here. Without special reason, you should always add
  309.     the above default log cleaners in the list.
  310.     </description>
  311.   </property>  
  312.   <property>
  313.     <name>hbase.regions.percheckin</name>
  314.     <value>10</value>
  315.     <description>Maximum number of regions that can be assigned in a single go
  316.     to a region server.
  317.     </description>
  318.   </property>
  319.   <property>
  320.     <name>hbase.server.thread.wakefrequency</name>
  321.     <value>10000</value>
  322.     <description>Time to sleep in between searches for work (in milliseconds).
  323.     Used as sleep interval by service threads such as META scanner and log roller.
  324.     </description>
  325.   </property>
  326.   <property>
  327.     <name>hbase.hregion.memstore.flush.size</name>
  328.     <value>67108864</value>
  329.     <description>
  330.     Memstore will be flushed to disk if size of the memstore
  331.     exceeds this number of bytes.  Value is checked by a thread that runs
  332.     every hbase.server.thread.wakefrequency.
  333.     </description>
  334.   </property>
  335.   <property>
  336.     <name>hbase.hregion.preclose.flush.size</name>
  337.     <value>5242880</value>
  338.     <description>
  339.       If the memstores in a region are this size or larger when we go
  340.       to close, run a "pre-flush" to clear out memstores before we put up
  341.       the region closed flag and take the region offline.  On close,
  342.       a flush is run under the close flag up to empty memory.  During
  343.       this time the region is offline and we are not taking on any writes.
  344.       If the memstore content large, this flush could take a long time to
  345.       complete.  The preflush is meant to clean out the bulk of the memstore
  346.       before putting up the close flag and taking the region offline so the
  347.       flush that runs under the close flag has little to do.
  348.     </description>
  349.   </property>
  350.   <property>
  351.     <name>hbase.hregion.memstore.block.multiplier</name>
  352.     <value>2</value>
  353.     <description>
  354.     Block updates if memstore has hbase.hregion.block.memstore
  355.     time hbase.hregion.flush.size bytes.  Useful preventing
  356.     runaway memstore during spikes in update traffic.  Without an
  357.     upper-bound, memstore fills such that when it flushes the
  358.     resultant flush files take a long time to compact or split, or
  359.     worse, we OOME.
  360.     </description>
  361.   </property>
  362.   <property>
  363.     <name>hbase.hregion.max.filesize</name>
  364.     <value>268435456</value>
  365.     <description>
  366.     Maximum HStoreFile size. If any one of a column families' HStoreFiles has
  367.     grown to exceed this value, the hosting HRegion is split in two.
  368.     Default: 256M.
  369.     </description>
  370.   </property>
  371.   <property>
  372.     <name>hbase.hstore.compactionThreshold</name>
  373.     <value>3</value>
  374.     <description>
  375.     If more than this number of HStoreFiles in any one HStore
  376.     (one HStoreFile is written per flush of memstore) then a compaction
  377.     is run to rewrite all HStoreFiles files as one.  Larger numbers
  378.     put off compaction but when it runs, it takes longer to complete.
  379.     During a compaction, updates cannot be flushed to disk.  Long
  380.     compactions require memory sufficient to carry the logging of
  381.     all updates across the duration of the compaction.
  382.  
  383.     If too large, clients timeout during compaction.
  384.     </description>
  385.   </property>
  386.   <property>
  387.     <name>hbase.hstore.blockingStoreFiles</name>
  388.     <value>7</value>
  389.     <description>
  390.     If more than this number of StoreFiles in any one Store
  391.     (one StoreFile is written per flush of MemStore) then updates are
  392.     blocked for this HRegion until a compaction is completed, or
  393.     until hbase.hstore.blockingWaitTime has been exceeded.
  394.     </description>
  395.   </property>
  396.   <property>
  397.     <name>hbase.hstore.blockingWaitTime</name>
  398.     <value>90000</value>
  399.     <description>
  400.     The time an HRegion will block updates for after hitting the StoreFile
  401.     limit defined by hbase.hstore.blockingStoreFiles.
  402.     After this time has elapsed, the HRegion will stop blocking updates even
  403.     if a compaction has not been completed.  Default: 90 seconds.
  404.     </description>
  405.   </property>
  406.   <property>
  407.     <name>hbase.hstore.compaction.max</name>
  408.     <value>10</value>
  409.     <description>Max number of HStoreFiles to compact per 'minor' compaction.
  410.     </description>
  411.   </property>
  412.   <property>
  413.     <name>hbase.hregion.majorcompaction</name>
  414.     <value>86400000</value>
  415.     <description>The time (in miliseconds) between 'major' compactions of all
  416.     HStoreFiles in a region.  Default: 1 day.
  417.     Set to 0 to disable automated major compactions.
  418.     </description>
  419.   </property>
  420.   <property>
  421.     <name>hbase.regions.slop</name>
  422.     <value>0.3</value>
  423.     <description>Rebalance if regionserver has average + (average * slop) regions.
  424.     Default is 30% slop.
  425.     </description>
  426.   </property>
  427.   <property>
  428.     <name>hfile.min.blocksize.size</name>
  429.     <value>65536</value>
  430.     <description>Minimum store file block size.  The smaller you make this, the
  431.     bigger your index and the less you fetch on a random-access.  Set size down
  432.     if you have small cells and want faster random-access of individual cells.
  433.     </description>
  434.   </property>
  435.   <property>
  436.       <name>hfile.block.cache.size</name>
  437.       <value>0.2</value>
  438.       <description>
  439.           Percentage of maximum heap (-Xmx setting) to allocate to block cache
  440.           used by HFile/StoreFile. Default of 0.2 means allocate 20%.
  441.           Set to 0 to disable.
  442.       </description>
  443.   </property>
  444.   <property>
  445.     <name>hbase.hash.type</name>
  446.     <value>murmur</value>
  447.     <description>The hashing algorithm for use in HashFunction. Two values are
  448.     supported now: murmur (MurmurHash) and jenkins (JenkinsHash).
  449.     </description>
  450.   </property>
  451.   <property>
  452.     <name>zookeeper.session.timeout</name>
  453.     <value>60000</value>
  454.     <description>ZooKeeper session timeout.
  455.       HBase passes this to the zk quorum as suggested maximum time for a
  456.       session.  See http://hadoop.apache.org/zookeeper/docs/current/zookeeperProgrammers.html#ch_zkSessions
  457.       "The client sends a requested timeout, the server responds with the
  458.       timeout that it can give the client. "
  459.       In milliseconds.
  460.     </description>
  461.   </property>
  462.   <property>
  463.     <name>zookeeper.retries</name>
  464.     <value>5</value>
  465.     <description>How many times to retry connections to ZooKeeper. Used for
  466.       reading/writing root region location.  Used together with ${zookeeper.pause}
  467.       in an exponential backoff fashion when making queries to ZooKeeper.
  468.     </description>
  469.   </property>
  470.   <property>
  471.     <name>zookeeper.pause</name>
  472.     <value>2000</value>
  473.     <description>Sleep time between retries to ZooKeeper. In milliseconds. Used
  474.       together with ${zookeeper.retries} in an exponential backoff fashion when
  475.       making queries to ZooKeeper.
  476.     </description>
  477.   </property>
  478.   <property>
  479.     <name>zookeeper.znode.parent</name>
  480.     <value>/hbase</value>
  481.     <description>Root ZNode for HBase in ZooKeeper. All of HBase's ZooKeeper
  482.       files that are configured with a relative path will go under this node.
  483.       By default, all of HBase's ZooKeeper file path are configured with a
  484.       relative path, so they will all go under this directory unless changed.
  485.     </description>
  486.   </property>
  487.   <property>
  488.     <name>zookeeper.znode.rootserver</name>
  489.     <value>root-region-server</value>
  490.     <description>Path to ZNode holding root region location. This is written by
  491.       the master and read by clients and region servers. If a relative path is
  492.       given, the parent folder will be ${zookeeper.znode.parent}. By default,
  493.       this means the root location is stored at /hbase/root-region-server.
  494.     </description>
  495.   </property>
  496.  
  497.   <!--
  498.   The following three properties are used together to create the list of
  499.   host:peer_port:leader_port quorum servers for ZooKeeper.
  500.   -->
  501.   <property>
  502.     <name>hbase.zookeeper.quorum</name>
  503.     <value>localhost</value>
  504.     <description>Comma separated list of servers in the ZooKeeper Quorum.
  505.     For example, "host1.mydomain.com,host2.mydomain.com,host3.mydomain.com".
  506.     By default this is set to localhost for local and pseudo-distributed modes
  507.     of operation. For a fully-distributed setup, this should be set to a full
  508.     list of ZooKeeper quorum servers. If HBASE_MANAGES_ZK is set in hbase-env.sh
  509.     this is the list of servers which we will start/stop ZooKeeper on.
  510.     </description>
  511.   </property>
  512.   <property>
  513.     <name>hbase.zookeeper.peerport</name>
  514.     <value>2888</value>
  515.     <description>Port used by ZooKeeper peers to talk to each other.
  516.     See http://hadoop.apache.org/zookeeper/docs/r3.1.1/zookeeperStarted.html#sc_RunningReplicatedZooKeeper
  517.     for more information.
  518.     </description>
  519.   </property>
  520.   <property>
  521.     <name>hbase.zookeeper.leaderport</name>
  522.     <value>3888</value>
  523.     <description>Port used by ZooKeeper for leader election.
  524.     See http://hadoop.apache.org/zookeeper/docs/r3.1.1/zookeeperStarted.html#sc_RunningReplicatedZooKeeper
  525.     for more information.
  526.     </description>
  527.   </property>
  528.   <!-- End of properties used to generate ZooKeeper host:port quorum list. -->
  529.  
  530.   <!--
  531.   Beginning of properties that are directly mapped from ZooKeeper's zoo.cfg.
  532.   All properties with an "hbase.zookeeper.property." prefix are converted for
  533.   ZooKeeper's configuration. Hence, if you want to add an option from zoo.cfg,
  534.   e.g.  "initLimit=10" you would append the following to your configuration:
  535.     <property>
  536.       <name>hbase.zookeeper.property.initLimit</name>
  537.       <value>10</value>
  538.     </property>
  539.   -->
  540.   <property>
  541.     <name>hbase.zookeeper.property.initLimit</name>
  542.     <value>10</value>
  543.     <description>Property from ZooKeeper's config zoo.cfg.
  544.     The number of ticks that the initial synchronization phase can take.
  545.     </description>
  546.   </property>
  547.   <property>
  548.     <name>hbase.zookeeper.property.syncLimit</name>
  549.     <value>5</value>
  550.     <description>Property from ZooKeeper's config zoo.cfg.
  551.     The number of ticks that can pass between sending a request and getting an
  552.     acknowledgment.
  553.     </description>
  554.   </property>
  555.   <property>
  556.     <name>hbase.zookeeper.property.dataDir</name>
  557.     <value>${hbase.tmp.dir}/zookeeper</value>
  558.     <description>Property from ZooKeeper's config zoo.cfg.
  559.     The directory where the snapshot is stored.
  560.     </description>
  561.   </property>
  562.   <property>
  563.     <name>hbase.zookeeper.property.clientPort</name>
  564.     <value>2181</value>
  565.     <description>Property from ZooKeeper's config zoo.cfg.
  566.     The port at which the clients will connect.
  567.     </description>
  568.   </property>
  569.   <property>
  570.     <name>hbase.zookeeper.property.maxClientCnxns</name>
  571.     <value>30</value>
  572.     <description>Property from ZooKeeper's config zoo.cfg.
  573.     Limit on number of concurrent connections (at the socket level) that a
  574.     single client, identified by IP address, may make to a single member of
  575.     the ZooKeeper ensemble. Set high to avoid zk connection issues running
  576.     standalone and pseudo-distributed.
  577.     </description>
  578.   </property>
  579.   <!-- End of properties that are directly mapped from ZooKeeper's zoo.cfg -->
  580. </configuration>
clone this paste RAW Paste Data