| #!/bin/sh |
| # |
| #/** |
| # * Copyright 2007 The Apache Software Foundation |
| # * |
| # * Licensed to the Apache Software Foundation (ASF) under one |
| # * or more contributor license agreements. See the NOTICE file |
| # * distributed with this work for additional information |
| # * regarding copyright ownership. The ASF licenses this file |
| # * to you under the Apache License, Version 2.0 (the |
| # * "License"); you may not use this file except in compliance |
| # * with the License. You may obtain a copy of the License at |
| # * |
| # * http://www.apache.org/licenses/LICENSE-2.0 |
| # * |
| # * Unless required by applicable law or agreed to in writing, software |
| # * distributed under the License is distributed on an "AS IS" BASIS, |
| # * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| # * See the License for the specific language governing permissions and |
| # * limitations under the License. |
| # */ |
| |
| ## Bookie settings |
| |
| # Port that bookie server listen on |
| bookiePort=3181 |
| |
| # Directory Bookkeeper outputs its write ahead log |
| journalDirectory=/tmp/bk-txn |
| |
| # Directory Bookkeeper outputs ledger snapshots |
| # could define multi directories to store snapshots, separated by ',' |
| # For example: |
| # ledgerDirectories=/tmp/bk1-data,/tmp/bk2-data |
| # |
| # Ideally ledger dirs and journal dir are each in a differet device, |
| # which reduce the contention between random i/o and sequential write. |
| # It is possible to run with a single disk, but performance will be significantly lower. |
| ledgerDirectories=/tmp/bk-data |
| |
| # Ledger Manager Class |
| # What kind of ledger manager is used to manage how ledgers are stored, managed |
| # and garbage collected. Try to read 'BookKeeper Internals' for detail info. |
| # ledgerManagerType=flat |
| |
| # Root zookeeper path to store ledger metadata |
| # This parameter is used by zookeeper-based ledger manager as a root znode to |
| # store all ledgers. |
| # zkLedgersRootPath=/ledgers |
| |
| # Max file size of entry logger, in bytes |
| # A new entry log file will be created when the old one reaches the file size limitation |
| # logSizeLimit=2147483648 |
| |
| # Threshold of minor compaction |
| # For those entry log files whose remaining size percentage reaches below |
| # this threshold will be compacted in a minor compaction. |
| # If it is set to less than zero, the minor compaction is disabled. |
| # minorCompactionThreshold=0.2 |
| |
| # Interval to run minor compaction, in seconds |
| # If it is set to less than zero, the minor compaction is disabled. |
| # minorCompactionInterval=3600 |
| |
| # Threshold of major compaction |
| # For those entry log files whose remaining size percentage reaches below |
| # this threshold will be compacted in a major compaction. |
| # Those entry log files whose remaining size percentage is still |
| # higher than the threshold will never be compacted. |
| # If it is set to less than zero, the minor compaction is disabled. |
| # majorCompactionThreshold=0.8 |
| |
| # Interval to run major compaction, in seconds |
| # If it is set to less than zero, the major compaction is disabled. |
| # majorCompactionInterval=86400 |
| |
| # Max file size of journal file, in mega bytes |
| # A new journal file will be created when the old one reaches the file size limitation |
| # |
| # journalMaxSizeMB=2048 |
| |
| # Max number of old journal file to kept |
| # Keep a number of old journal files would help data recovery in specia case |
| # |
| # journalMaxBackups=5 |
| |
| # How long the interval to trigger next garbage collection, in milliseconds |
| # Since garbage collection is running in background, too frequent gc |
| # will heart performance. It is better to give a higher number of gc |
| # interval if there is enough disk capacity. |
| # gcWaitTime=1000 |
| |
| # How long the interval to flush ledger index pages to disk, in milliseconds |
| # Flushing index files will introduce much random disk I/O. |
| # If separating journal dir and ledger dirs each on different devices, |
| # flushing would not affect performance. But if putting journal dir |
| # and ledger dirs on same device, performance degrade significantly |
| # on too frequent flushing. You can consider increment flush interval |
| # to get better performance, but you need to pay more time on bookie |
| # server restart after failure. |
| # |
| # flushInterval=100 |
| |
| # Interval to watch whether bookie is dead or not, in milliseconds |
| # |
| # bookieDeathWatchInterval=1000 |
| |
| ## zookeeper client settings |
| |
| # A list of one of more servers on which zookeeper is running. |
| # The server list can be comma separated values, for example: |
| # zkServers=zk1:2181,zk2:2181,zk3:2181 |
| zkServers=localhost:2181 |
| # ZooKeeper client session timeout in milliseconds |
| # Bookie server will exit if it received SESSION_EXPIRED because it |
| # was partitioned off from ZooKeeper for more than the session timeout |
| # JVM garbage collection, disk I/O will cause SESSION_EXPIRED. |
| # Increment this value could help avoiding this issue |
| zkTimeout=10000 |
| |
| ## NIO Server settings |
| |
| # This settings is used to enabled/disabled Nagle's algorithm, which is a means of |
| # improving the efficiency of TCP/IP networks by reducing the number of packets |
| # that need to be sent over the network. |
| # If you are sending many small messages, such that more than one can fit in |
| # a single IP packet, setting server.tcpnodelay to false to enable Nagle algorithm |
| # can provide better performance. |
| # Default value is true. |
| # |
| # serverTcpNoDelay=true |
| |
| ## ledger cache settings |
| |
| # Max number of ledger index files could be opened in bookie server |
| # If number of ledger index files reaches this limitation, bookie |
| # server started to swap some ledgers from memory to disk. |
| # Too frequent swap will affect performance. You can tune this number |
| # to gain performance according your requirements. |
| # openFileLimit=900 |
| |
| # Size of a index page in ledger cache, in bytes |
| # A larger index page can improve performance writing page to disk, |
| # which is efficent when you have small number of ledgers and these |
| # ledgers have similar number of entries. |
| # If you have large number of ledgers and each ledger has fewer entries, |
| # smaller index page would improve memory usage. |
| # pageSize=8192 |
| |
| # How many index pages provided in ledger cache |
| # If number of index pages reaches this limitation, bookie server |
| # starts to swap some ledgers from memory to disk. You can increment |
| # this value when you found swap became more frequent. But make sure |
| # pageLimit*pageSize should not more than JVM max memory limitation, |
| # otherwise you would got OutOfMemoryException. |
| # In general, incrementing pageLimit, using smaller index page would |
| # gain bettern performance in lager number of ledgers with fewer entries case |
| # If pageLimit is -1, bookie server will use 1/3 of JVM memory to compute |
| # the limitation of number of index pages. |
| # pageLimit=-1 |
| |
| #If all ledger directories configured are full, then support only read requests for clients. |
| #If "readOnlyModeEnabled=true" then on all ledger disks full, bookie will be converted |
| #to read-only mode and serve only read requests. Otherwise the bookie will be shutdown. |
| #By default this will be disabled. |
| #readOnlyModeEnabled=false |
| |
| #For each ledger dir, maximum disk space which can be used. |
| #Default is 0.95f. i.e. 95% of disk can be used at most after which nothing will |
| #be written to that partition. If all ledger dir partions are full, then bookie |
| #will turn to readonly mode if 'readOnlyModeEnabled=true' is set, else it will |
| #shutdown. |
| #Valid values should be in between 0 and 1 (exclusive). |
| #diskUsageThreshold=0.95 |
| |
| #Disk check interval in milli seconds, interval to check the ledger dirs usage. |
| #Default is 10000 |
| #diskCheckInterval=10000 |
| |
| # Interval at which the auditor will do a check of all ledgers in the cluster. |
| # By default this runs once a week. The interval is set in seconds. |
| # To disable the periodic check completely, set this to 0. |
| # Note that periodic checking will put extra load on the cluster, so it should |
| # not be run more frequently than once a day. |
| #auditorPeriodicCheckInterval=604800 |