forked from EventStore/EventStore.JVM
-
Notifications
You must be signed in to change notification settings - Fork 0
/
reference.conf
139 lines (104 loc) · 3.94 KB
/
reference.conf
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
eventstore {
# IP & port of Event Store
address {
host = "127.0.0.1"
port = 1113
}
http {
protocol = "http"
port = 2113
prefix = ""
}
# The desired connection timeout
connection-timeout = 1s
# Maximum number of reconnections before backing, -1 to reconnect forever
max-reconnections = 100
reconnection-delay {
# Delay before first reconnection
min = 250ms
# Maximum delay on reconnections
max = 10s
}
# The default credentials to use for operations where others are not explicitly supplied.
credentials {
login = "admin"
password = "changeit"
}
heartbeat {
# The interval at which to send heartbeat messages.
interval = 500ms
# The interval after which an unacknowledged heartbeat will cause the connection to be considered faulted and disconnect.
timeout = 5s
}
operation {
# The maximum number of operation retries
max-retries = 10
# The amount of time before an operation is considered to have timed out
timeout = 30s
}
# Whether to resolve LinkTo events automatically
resolve-linkTos = false
# Whether or not to require EventStore to refuse serving read or write request if it is not master
require-master = true
# Number of events to be retrieved by client as single message
read-batch-size = 500
# The size of the buffer in element count
buffer-size = 100000
# Strategy that is used when elements cannot fit inside the buffer
# Possible values DropHead, DropTail, DropBuffer, DropNew, Fail
buffer-overflow-strategy = "Fail"
# The number of serialization/deserialization functions to be run in parallel
serialization-parallelism = 8
# Serialization done asynchronously and these futures may complete in any order,
# but results will be used with preserved order if set to true
serialization-ordered = true
cluster {
# Endpoints for seeding gossip
# For example: ["127.0.0.1:1", "127.0.0.2:2"]
gossip-seeds = []
# The DNS name to use for discovering endpoints
dns = null
# The time given to resolve dns
dns-lookup-timeout = 2s
# The well-known endpoint on which cluster managers are running
external-gossip-port = 30778
# Maximum number of attempts for discovering endpoints
max-discover-attempts = 10
# The interval between cluster discovery attempts
discover-attempt-interval = 500ms
# The interval at which to keep discovering cluster
discovery-interval = 1s
# Timeout for cluster gossip
gossip-timeout = 1s
}
persistent-subscription {
# Whether to resolve LinkTo events automatically
resolve-linkTos = false
# Where the subscription should start from (position)
start-from = last
# Whether or not in depth latency statistics should be tracked on this subscription.
extra-statistics = false
# The amount of time after which a message should be considered to be timedout and retried.
message-timeout = 30s
# The maximum number of retries (due to timeout) before a message get considered to be parked
max-retry-count = 500
# The size of the buffer listening to live messages as they happen
live-buffer-size = 500
# The number of events read at a time when paging in history
read-batch-size = 10
# The number of events to cache when paging through history
history-buffer-size = 20
# The amount of time to try to checkpoint after
checkpoint-after = 2s
# The minimum number of messages to checkpoint
min-checkpoint-count = 10
# The maximum number of messages to checkpoint if this number is a reached a checkpoint will be forced.
max-checkpoint-count = 1000
# The maximum number of subscribers allowed
max-subscriber-count = 0
# The [[ConsumerStrategy]] to use for distributing events to client consumers
# Known are RoundRobin, DispatchToSingle
# however you can provide a custom one, just make sure it is supported by server
consumer-strategy = RoundRobin
}
}