-
Notifications
You must be signed in to change notification settings - Fork 137
Brooklin Configuration
Ahmed Elbahtemy edited this page Apr 20, 2019
·
11 revisions
-
The listing below documents all configuration properties of the Brooklin server application. However, it does not capture properties specific to certain
Connectors
orTransportProviders
. These can be found on the individual wiki pages of the respective modules. -
These properties are typically provided to Brooklin through a Java properties file. An example is located at https://github.com/linkedin/brooklin/blob/master/config/server.properties
- Fully-qualified
Connector
factory class name - Factory class must implement the
ConnectorFactory
interface. -
<connectorName>
must match one of the names specified inbrooklin.server.connectorNames
- One such property is required for every
Connector
name specified inbrooklin.server.connectorNames
- Please refer to individual
Connector
wiki pages for specific config properties
- A comma-separated list of
Connector
names -
Connector
names can be arbitrary strings -
Connector
names are used to identify them in configuration options andDatastream
operations - At least one
Connector
name must be provided
- Brooklin cluster name
- Also the name of the top-level znode for a Brooklin cluster in ZooKeeper
- ZooKeeper URL
- Address of ZooKeeper instance to use for maintaining metadata about
Coordinators
,Datastreams
, andDatastreamTasks
- Metrics reports directory
- Directory where CSV metrics reports are generated
- Datastream Management Service (DMS) health-monitoring REST endpoint path
- Default is empty string
- Datastream Management Service (DMS) health-monitoring REST endpoint port
- Default is
brooklin.server.httpPort
- Datastream Management Service (DMS) port
- This is the port used by the
HttpJettyServer
of the DMS service - Specifying 0 causes a port to be selected at random (default)
- Fully-qualified
SerDe
factory class name - Factory class must implement the
SerdeAdminFactory
interface - Not required unless
brooklin.server.serdeNames
is non-empty -
<serdeName>
must match one of the names specified inbrooklin.server.serdeNames
- One such property is required for every
SerDe
name specified inbrooklin.server.serdeNames
- A comma-separated list of
SerDe
(Serializer/Deserializer) names -
SerDe
names can be arbitrary strings -
SerDe
names are used to identify them in configuration options andDatastream
operations
- Fully-qualified
TransportProvider
factory class name - Factory class must implement the
TransportProviderAdminFactory
interface -
<transportProviderName>
must match one of the names specified inbrooklin.server.transportProviderNames
- One such property is required for every
Connector
name specified inbrooklin.server.transportProviderNames
- Please refer to individual
TransportProvider
wiki pages for specific config properties
- A comma-separated list of
TransportProvider
names -
TransportProvider
names can be arbitrary strings -
TransportProvider
names are used to identify them in configuration options andDatastream
operations - At least one
TransportProvider
name must be provided
- Home
- Brooklin Architecture
- Production Use Cases
- Developer Guide
- Documentation
- REST Endpoints
- Connectors
- Transport Providers
- Brooklin Configuration
- Test Driving Brooklin