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
|
###
# ============LICENSE_START=======================================================
# feature-pooling-dmaap
# ================================================================================
# Copyright (C) 2018-2020 AT&T Intellectual Property. All rights reserved.
# ================================================================================
# Licensed 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.
# ============LICENSE_END=========================================================
###
# In general, the feature-specific properties begin with "pooling",
# and they may be made specific to a controller by prepending with
# "pooling.<controller-name>", instead.
#
# The available properties and their default values are shown below.
# Whether or not the feature is enabled.
#pooling.enabled=false
# The internal DMaaP topic used by a controller. Note: the controller
# name is required for this property.
#pooling.<controller-name>.topic =
# Maximum number of events to retain in the queue while a new host waits
# to be assigned work.
#pooling.offline.queue.limit=1000
# Maximum age, in milliseconds, of events to be retained in the queue.
# Events older than this are discarded.
#pooling.offline.queue.age.milliseconds=60000
# Time, in milliseconds, to wait for an "Offline" message to be published
# to DMaaP before the connection may be closed.
#pooling.offline.publish.wait.milliseconds=3000
# Time, in milliseconds, to wait for this host's initial heart beat. This
# is used to verify connectivity to the internal DMaaP topic.
#pooling.start.heartbeat.milliseconds=100000
# Time, in milliseconds, to wait before attempting to re-active this
# host when it was not assigned any work.
#pooling.reactivate.milliseconds=50000
# Time, in milliseconds, to wait for other hosts to identify themselves
# when this host is started.
#pooling.identification.milliseconds=50000
# Time, in milliseconds, to wait for heart beats from this host, or its
# predecessor, during the active state.
#pooling.active.heartbeat.milliseconds=50000
# Time, in milliseconds, to wait between heart beat generations.
#pooling.inter.heartbeat.milliseconds=15000
# Topic used for inter-host communication for a particular controller
# pooling.<controller-name>.topic=XXX
# Each controller that is enabled should have its own topic and the
# corresponding dmaap.xxx properties. However, for now, just assume that
# the usecases features will not both be enabled at the same time.
pooling.usecases.enabled=true
pooling.usecases.topic=${env:POOLING_TOPIC}
# the list of sources and sinks should be identical
dmaap.source.topics=POOLING_TOPIC
dmaap.sink.topics=POOLING_TOPIC
dmaap.source.topics.POOLING_TOPIC.servers=${env:DMAAP_SERVERS}
dmaap.source.topics.POOLING_TOPIC.effectiveTopic=${env:POOLING_TOPIC}
dmaap.source.topics.POOLING_TOPIC.apiKey=
dmaap.source.topics.POOLING_TOPIC.apiSecret=
dmaap.sink.topics.POOLING_TOPIC.servers=${env:DMAAP_SERVERS}
dmaap.sink.topics.POOLING_TOPIC.effectiveTopic=${env:POOLING_TOPIC}
dmaap.sink.topics.POOLING_TOPIC.apiKey=
dmaap.sink.topics.POOLING_TOPIC.apiSecret=
|
