Influxdata
/
influxdb
mirror of https://github.com/influxdata/influxdb.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Increase default buffer sizes to make replays less likely.

pull/290/head
Paul Dix 2014-02-27 15:17:27 -05:00
parent e4c039b3b8
commit 47058eb0e8
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
config.toml.sample
View File

@ -38,7 +38,7 @@ dir = "/tmp/influxdb/development/db"
# How many requests to potentially buffer in memory. If the buffer gets filled then writes
# will still be logged and once the local storage has caught up (or compacted) the writes
# will be replayed from the WAL
write-buffer-size = 1000
write-buffer-size = 10000
[cluster]
# A comma separated list of servers to seed
@ -62,11 +62,11 @@ protobuf_heartbeat = "200ms" # the heartbeat interval between the servers. must
# How many write requests to potentially buffer in memory per server. If the buffer gets filled then writes
# will still be logged and once the server has caught up (or come back online) the writes
# will be replayed from the WAL
write-buffer-size = 1000
write-buffer-size = 10000
# When queries get distributed out, the go in parallel. However, the responses must be sent in time order.
# This setting determines how many responses can be buffered in memory per shard before data starts gettind dropped.
query-shard-buffer-size = 500
query-shard-buffer-size = 1000
[leveldb]

6
src/configuration/config.toml
View File

@ -35,7 +35,7 @@ dir = "/tmp/influxdb/development/db"
# How many requests to potentially buffer in memory. If the buffer gets filled then writes
# will still be logged and once the local storage has caught up (or compacted) the writes
# will be replayed from the WAL
write-buffer-size = 1000
write-buffer-size = 10000
[cluster]
# A comma separated list of servers to seed
@ -59,11 +59,11 @@ protobuf_heartbeat = "200ms" # the heartbeat interval between the servers. must
# How many write requests to potentially buffer in memory per server. If the buffer gets filled then writes
# will still be logged and once the server has caught up (or come back online) the writes
# will be replayed from the WAL
write-buffer-size = 1000
write-buffer-size = 10000
# When queries get distributed out, the go in parallel. However, the responses must be sent in time order.
# This setting determines how many responses can be buffered in memory per shard before data starts gettind dropped.
query-shard-buffer-size = 500
query-shard-buffer-size = 1000
[leveldb]