2 # ============LICENSE_START=======================================================
3 # feature-pooling-messages
4 # ================================================================================
5 # Copyright (C) 2018-2020 AT&T Intellectual Property. All rights reserved.
6 # Modifications Copyright (C) 2024 Nordix Foundation.
7 # ================================================================================
8 # Licensed under the Apache License, Version 2.0 (the "License");
9 # you may not use this file except in compliance with the License.
10 # You may obtain a copy of the License at
12 # http://www.apache.org/licenses/LICENSE-2.0
14 # Unless required by applicable law or agreed to in writing, software
15 # distributed under the License is distributed on an "AS IS" BASIS,
16 # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
17 # See the License for the specific language governing permissions and
18 # limitations under the License.
19 # ============LICENSE_END=========================================================
22 # In general, the feature-specific properties begin with "pooling",
23 # and they may be made specific to a controller by prepending with
24 # "pooling.<controller-name>", instead.
26 # The available properties and their default values are shown below.
28 # Whether the feature is enabled.
29 #pooling.enabled=false
31 # The internal kafka topic used by a controller. Note: the controller
32 # name is required for this property.
33 #pooling.<controller-name>.topic =
35 # Maximum number of events to retain in the queue while a new host waits
36 # to be assigned work.
37 #pooling.offline.queue.limit=1000
39 # Maximum age, in milliseconds, of events to be retained in the queue.
40 # Events older than this are discarded.
41 #pooling.offline.queue.age.milliseconds=60000
43 # Time, in milliseconds, to wait for an "Offline" message to be published
44 # to topic manager before the connection may be closed.
45 #pooling.offline.publish.wait.milliseconds=3000
47 # Time, in milliseconds, to wait for this host's initial heart beat. This
48 # is used to verify connectivity to the internal topic.
49 #pooling.start.heartbeat.milliseconds=100000
51 # Time, in milliseconds, to wait before attempting to reactivate this
52 # host when it was not assigned any work.
53 #pooling.reactivate.milliseconds=50000
55 # Time, in milliseconds, to wait for other hosts to identify themselves
56 # when this host is started.
57 #pooling.identification.milliseconds=50000
59 # Time, in milliseconds, to wait for heart beats from this host, or its
60 # predecessor, during the active state.
61 #pooling.active.heartbeat.milliseconds=50000
63 # Time, in milliseconds, to wait between heart beat generations.
64 #pooling.inter.heartbeat.milliseconds=15000
66 # Topic used for inter-host communication for a particular controller
67 # pooling.<controller-name>.topic=XXX
69 # Each controller that is enabled should have its own topic and the
70 # corresponding ${topicManager}.xxx properties (using kafka as default).
71 # However, for now, just assume that the usecases features will not both
72 # be enabled at the same time.
74 pooling.usecases.enabled=true
75 pooling.usecases.topic=${env:POOLING_TOPIC}
77 # the list of sources and sinks should be identical
78 kafka.source.topics=POOLING_TOPIC
79 kafka.sink.topics=POOLING_TOPIC
81 kafka.source.topics.POOLING_TOPIC.servers=${env:KAFKA_SERVERS}
82 kafka.source.topics.POOLING_TOPIC.effectiveTopic=${env:POOLING_TOPIC}
83 kafka.source.topics.POOLING_TOPIC.apiKey=
84 kafka.source.topics.POOLING_TOPIC.apiSecret=
86 kafka.sink.topics.POOLING_TOPIC.servers=${env:kafka_SERVERS}
87 kafka.sink.topics.POOLING_TOPIC.effectiveTopic=${env:POOLING_TOPIC}
88 kafka.sink.topics.POOLING_TOPIC.apiKey=
89 kafka.sink.topics.POOLING_TOPIC.apiSecret=