This binary provider is not independent and will always be used as part of a more complex template chain of providers. In case of a failure in a read or write operation, this binary provider notifies its parent provider in the hierarchy.
The remote Binary Provider links a node to all other nodes in the cluster, meaning it enables each node to 'see' the filestore of every other node.
Remote Binary Provider Template
The following table lists the elements in the remote binary provider template.
Parameter | Description |
|---|---|
type | remote |
connectionTimeout | Default: 5000 ms Time before timing out an outgoing connection. |
socketTimeout | Default: 15000 ms Time before timing out an established connection (i.e. no data is sent over the wire). |
maxConnections | Default: 200 Maximum outgoing connections from the provider. |
connectionRetry | Default: 2 How many times to retry connecting to the remote endpoint. |
zone | The name of the sharding zone the provider is part of (only applicable under a sharding provider). |
checkPeriod | Default: 15000 ms The minimum time to wait between trying to re-activate the provider if it had fatal errors at any point. |
Remote Binary Provider Example
The following is an example of how a remote binary provider may be configured. To see how this can be integrated with a complete binarystore.xml configuration, please refer to the example under Sharding-Cluster Binary Provider.
<provider id="remote" type="remote">
<checkPeriod>15000</checkPeriod>
<connectionTimeout>5000</connectionTimeout>
<socketTimeout>15000</socketTimeout>
<maxConnections>200</maxConnections>
<connectionRetry>2</connectionRetry>
<zone>remote</zone>
</provider>