services.xml - container

This is the reference for container cluster configuration:

container [version, id]
    http
        server [id, port]
        filtering
    handler [id, class, bundle]
        binding
        component
    server [id, class, bundle]
    components
    component
    search
        include [dir]
        binding
        searcher
        federation
        provider
        chain
        renderer
        threadpool
        significance
    document-processing
        include [dir]
        documentprocessor
        chain
    processing
        include [dir]
        binding
        processor
        chain
        renderer
    document-api
        abortondocumenterror
        retryenabled
        route
        maxpendingdocs
        maxpendingbytes
        retrydelay
        timeout
        tracelevel
        mbusport
        ignore-undefined-fields
    model-evaluation
        onnx
    document [type, class, bundle]
    accesslog [type, fileNamePattern, symlinkName, rotationInterval, rotationScheme]
    config
    nodes [allocated-memory, jvm-gc-options, jvm-options]
        environment-variables
        jvm [allocated-memory, options, gc-options]
        node [hostalias]
    secret-store [type]
        group [name, environment]
    zookeeper

Contained in services, zero or more container elements. The root element of a container cluster definition. Most elements takes optional config elements.

Attribute	Required	Value	Default	Description
version	required	number		1.0 in this version of Vespa
id	required	string		logical name of this cluster

Example:

<container id="default" version="1.0">
    <search>
        <chain id="default">
            <searcher id="com.mydomain.SimpleSearcher" bundle="the name in <artifactId> in pom.xml"/>
        </chain>
    </search>
    <nodes>
        <node hostalias="node1"/>
    </nodes>
</container>

Each container cluster has a default http server port, unless it contains a http element. Hence, when running more than one container cluster on the same node, it is necessary to manually assign a port to the http server to all but one cluster. Otherwise, the application will not deploy. Assigning a port is done by adding a server element with an explicit port number:

<container id="cluster2" version="1.0">
    <http>
        <server id="myServer" port="8081" />
    </http>
    ...
</container>

handler

The handler element holds the configuration of a request handler. For each binding tag, the handler will be bound to the pertinent JDisc interfaces using the given binding.

binding For JDisc request handlers, add this server binding to this handler.
component for injecting another component. Must be a declaration of a new component, not a reference.

Attribute	Required	Value	Description
id	required	string	The component ID
class	optional	string	The class of the handler, defaults to id
bundle	optional	string	The bundle to load the handler from: The name in <artifactId> in pom.xml. Defaults to class or id (if no class is given)

Example:

<container id="default" version="1.0">
    <handler id="com.yahoo.search.handler.LegacyBridge">
        <binding>http://*/*</binding>
    </handler>
    <handler bundle="the name in <artifactId> in pom.xml" id="com.mydomain.vespatest.RedirectingHandler"/>
    <handler bundle="the name in <artifactId> in pom.xml" id="com.mydomain.vespatest.ExampleHandler"/>
    <nodes>
        <node hostalias="node1"/>
    </nodes>
</container>

binding

The URI to map a Handler to. Multiple elements are allowed. See example above.

server

The server element holds the configuration of a JDisc server provider.

Attribute	Required	Value	Description
id	required	string	The component ID
class	optional	string	The class of the server, defaults to id
bundle	optional	string	The bundle to load the server from: The name in <artifactId> in the pom.xml. Defaults to class or id (if no class is given).

Example:

<server id="com.mydomain.vespatest.DemoServer">
    <config name="vespatest.demo-server">
        <response>Hello, world!
        </response>
        <port>16889</port>
    </config>
</server>

components

Contains component elements. Can be used in conjunction with include for modular config of components.

component

The component element holds the configuration of a generic component. Must be a declaration of a new component, not a reference.

Nested component child elements can be added for injecting specific component instances. This is useful if there is more than one declared component of the same Java class. Refer to Injecting components for details and examples.

Attribute	Required	Value	Description
id	required	string	The component ID
class	optional	string	The class of the component, defaults to id
bundle	optional	string	The bundle to load the component from: The name in <artifactId> in the pom.xml. Defaults to class or id (if no class is given).

Example:

<component id="com.mydomain.demo.DemoComponent" bundle="the name in <artifactId> in pom.xml" />

document-api

Use to enable Document API operations to a container cluster. Children elements:

Name	Required	Value	Default	Description
binding	optional	string	http://*/	The URI to map the document-api handlers to. Multiple bindings are valid. Must end with a '/'. Note that each document-api handler will get its individual binding by adding a suffix, e.g. the feed handler will add 'feed/', the remove handler will add 'remove/' and so on. Example: <document-api> <binding>http:///document-api/</binding> <binding>https:///document-api/</binding> </document-api> With these configured bindings, the feed handler will be available at `http:///document-api/feed/` and `https:///document-api/feed/`. For other handlers, just replace 'feed/' with the appropriate suffix, e.g. 'get/', 'remove/' etc.
abortondocumenterror	optional	true/false	true	Controls whether to abort the entire feed or not if a document-related error occurs, i.e. if a document contains an unknown field. Setting this field to `true` will abort the feed on such errors, while setting it to `false` will cause Vespa to simply skip to the next document in the feed. Note that malformed XML in the input will abort the feed regardless of this setting.
maxpendingbytes	optional	number		The maximum number of pending bytes. If `<maxpendingdocs>` is 0 and this is set to 0, this defaults to 100 MB. If `<maxpendingdocs>` is more than 0, and this is set to 0, the send-window is only limited by number of messages sent, not the memory footprint.
maxpendingdocs	optional	number		The maximum number of pending documents the client can have. By default, the client will dynamically adjust the window size based on the latency of the performed operations. If the parameter is set, dynamic window sizing will be turned off in favor of the configured value.
mbusport	optional	number		Set the MessageBus port
retrydelay	optional	double	1.0	Delay in seconds between retries
retryenabled	optional	true/false		Enable or disable retrying documents that have failed.
route	optional	string	default	Set the route to feed documents to
timeout	optional	double	180.0	Set the timeout value in seconds for an operation
tracelevel	optional	0-9	0	Configure the level of which to trace messages sent. The higher the level, the more detailed descriptions.
ignore-undefined-fields	optional	true/false	false	Set to true to ignore undefined fields in document API operations and let such operations complete successfully, rather than fail. A response header is returned when field operations are ignored.

Example:

<document-api>
    <binding>http://*/document-api/</binding>
    <binding>https://*/document-api/</binding>
    <abortondocumenterror>false</abortondocumenterror>
    <maxpendingbytes>1048576</maxpendingbytes>
    <maxpendingdocs>1000</maxpendingdocs>
    <mbusport>1234</mbusport>
    <retrydelay>5.5</retrydelay>
    <retryenabled>false</retryenabled>
    <route>default</route>
    <timeout>250.5</timeout>
    <tracelevel>3</tracelevel>
<document-api>

document

Concrete document type bindings for the container. Example:

<container id="default" version="1.0">
    <document class="com.mydomain.concretedocs.Vehicle"
              bundle="the name in <artifactId> in pom.xml"
              type="vehicle"/>
    <document class="com.mydomain.concretedocs.Vehicle"
              bundle="the name in <artifactId> in pom.xml"
              type="ship"/>
    <document class="com.mydomain.concretedocs2.Disease"
              bundle="the name in <artifactId> in pom.xml"
              type="disease"/>
    <search/>
    <document-processing>
        <chain id="default">
            <documentprocessor bundle="the name in <artifactId> in pom.xml"
                               id="concretedocs.ConcreteDocDocProc"/>
        </chain>
    </document-processing>
    <nodes>
        <node hostalias="node1"/>
    </nodes>
</container>

accesslog

Configures properties of the accesslog. The default type is json that will give output in (line-based) JSON format. See Access logging for configuration details. Setting the type to vespa gives a classic Apache CLF-like format.

Access logging can be disabled by setting the type to disabled.

Attribute	Required	Value	Default	Description
type	optional	string	json	The accesslog type: json, vespa or disabled
fileNamePattern	required*	string	JsonAccessLog.<container id>.%Y%m%d%H%M%S	File name pattern. * Note: Optional when type is disabled
symlinkName	optional	string	JsonAccessLog.<container id>	Symlink name
rotationInterval	optional	string	0 60 ...	Rotation interval
rotationScheme	optional	string	date	Valid values are date or sequence

Example:

<accesslog fileNamePattern="$VESPA_HOME/logs/vespa/access/JsonAccessLog.<container id>.%Y%m%d%H%M%S"
           symlinkName="JsonAccessLog.<container id>"
           rotationInterval="0 1 ..."
           type="vespa" />

include

Allows including XML snippets contained in external files. All files from all listed directories will be included. All files must have the same outer tag as they were referred from, i.e. search, document-processing or processing. The path must be relative to the application package root, and must never point outside the package.

Attribute	Required	Value	Default	Description
dir	required	string		The directory to include files from. File inclusion order is undefined.

Example:

<include dir="included_configs/search" />

nodes

The nodes element specifies the nodes that comprise this container cluster by adding node children.

Attribute	Required	Value	Description
allocated-memory	optional	percentage	Deprecated: See jvm.
jvm-options	optional	string	Deprecated: See jvm.
jvm-gc-options	optional	string	Deprecated: See jvm.

environment-variables

Add children elements to nodes for environment variables - see example below. These are set before the services are started on the container node - available for the Container.

jvm

JVM settings for container nodes:

Attribute	Required	Value	Description
allocated-memory	optional	percentage	Memory to allocate to each JVM instance as a percentage of available memory. Must be an integer percentage followed by %
options	optional	string	Generic JVM options
gc-options	optional	string	JVM GC options. Garbage Collector specific parameters

Example where 50% of the node total memory is used as the Max heap size of the JVM:

<nodes>
    <jvm gc-options="-XX:+UseG1GC -XX:MaxTenuringThreshold=10"
         options="-XX:+PrintCommandLineFlags"
         allocated-memory="50%" />
</nodes>

node

Attribute	Required	Value	Default	Description
hostalias	required	string		logical hostname - mapped to hostnames in hosts.xml

Example:

<nodes>
    <environment-variables>
        <KMP_SETTING>1</KMP_SETTING>
        <KMP_AFFINITY>granularity=fine,verbose,compact,1,0</KMP_AFFINITY>
    </environment-variables>
    <node hostalias="searchnode1" />
</nodes>

secret-store

The secret-store element holds configuration for custom implementations. Contains one or more group elements.

Attribute	Required	Value	Default	Description
type	required	string		Value: "oath-ckms"

group

Attribute	Required	Value	Default	Description
name	required	string		Key group name
environment	required	string		Value one of: "alpha" "corp" "prod" "aws" "aws_stage"

Example:

<secret-store type="my-ckms">
    <group name="[key group]" environment="[environment]"/>
</secret-store>

zookeeper

The zookeeper element declares that the container cluster should run ZooKeeper and configure the necessary components. This element has no attributes or children.