Open topic with navigation
default.properties file sets configuration options for the NuoDB broker or agent. It resides in the
domainPassword properties are required. Brokers and agents do not start unless these properties are set. The other properties in
default.properties are optional.
Leading and trailing whitespace in the setting of all properties in
default.properties is ignored.
default.propertiesfile without write permissions, you receive an error message that states that another program has access to the file. To resolve this, grant write permissions to the
flag specifies whether the alternate address should be advertised instead of the locally observed network addresses (as determined by a
When a broker advertises its own alternate address, it also advertises the alternate address of each broker to which it is peered and which also
At startup, a broker or agent logs the address that is returned from
2015-01-19T15:33:33.833+0000 INFO PeerContainerImpl.<init> (main) peer unstableId=[8343c7db-d60a-4382-a40c-6c0c68d7ac3e], peer=[220.127.116.11:48004], port=48004, raft=true, address=[ip-172-31-5-193/172.31.5.193:48004], addrToAdvertise=[18.104.22.168]
Note that in this release, each host in a domain runs a broker.
This property applies only to the initial entry of a broker into the domain. By default, a broker shuts down if its attempt to peer into the domain fails. By setting this property, a broker continues to try to peer into the domain until this timeout (in milliseconds) has elapsed. If the timeout elapses and the broker has not been able to peer into the domain then the broker shuts down.
backward compatibility, the default is to not retry (
This option is not related to agent reconnect when its peer broker disconnects.
An alternate address to use in identifying this host. To advertise this address, set the
property specifying the SQL connection load balancer that this broker
should use. The balancer determines how the broker chooses which
transaction engine (TE) to use for a SQL client connection. This
property has no effect on an agent.
Available load balancers are:
|Not set||The location of the directory that holds the
||Specifies whether this agent should be run as a broker. In this release, this should always be
||Specifies the name of the client connection property that specifies the process group that you want the broker to use when
||The name used to identify the domain to which this broker or agent belongs. This property must be set for the broker or agent to start.|
|Not set||Password used by this broker or agent to join the domain. This property must be set for the broker or agent to start.
Every broker and agent in a domain uses the same password to peer into the domain. In other words, the
For security reasons, there is no default password. As with all properties in
||If this property is set to
and agents ping their connected peer(s) periodically. A peer sends a
warning to its agent log if it does not receive acknowledgment of its
initial ping after 10 seconds and then continually after that.
The default behavior,
A setting of
For a peer to disconnect a non-responsive peer, the
A broker reports disconnected peers to all reachable brokers in the domain. Disconnected peers periodically try to reconnect. A broker tries to peer back into the domain according to the durable domain configuration. An agent tries to reconnect to another broker in the domain.
On this peer's host, execution of the NuoDB Manager
|hostTags=tag=value[, tag=value]...||Not set||Set this property to inject host tags into the broker or agent. The format is a comma-separated list of
|localBindAddress||Not set||For internal use only. Do not set this property.|
The log level for the broker or agent log output. Valid levels are, from most verbose to least verbose:
||The number of seconds that NuoDB waits for a process (TE, SM, SSM) to start. You should never set this property to be less than 30 seconds.|
|peer=peer[,peer]...||Not set||Specifies the host name and optionally a port for an existing broker, already running in the domain, to which this broker or agent should connect when joining the domain. A broker accepts only a single peer specification. On restart, a broker tries to connect to the broker specified by its peer setting. If that peer is unreachable, the broker falls back to its last-known state of brokers. If you are using non-default port settings, be sure to include the port number with the name or address of the peer.|
||When a broker starts it tries to connect to the broker specified by the
||When a broker starts it must connect to the domain peer specified by the
||The port that this broker or agent listens on for all incoming connections. If no value is specified, the broker or agent randomly selects an available port on which to listen. Enable this setting when you need to limit the openings in your firewall and AWS security policies.|
||A range of port numbers that
Specifying a start without an end indicates that process TCP/IP ports are assigned incrementally from the start without limit.
Each new process (transaction engine, storage manager, snapshot storage manager) that is started on a machine is communicated with by means of an assigned TCP/IP port that is specified through this property. Ensure firewall rules allow access from other machines.
Upon restart, a broker or agent runs a Domain State Machine resync protocol to remove process entries for any database processes that shut down while the local broker or agent was not running. Also, the restarted broker or agent waits for processes to reconnect and then reconciles the process ID list with the process entries in the DSM. Starting a database process is allowed only after the process reconnect window and the DSM resync. It can be as much as 10 seconds for any local process to reconnect. See also How Creation of Extra Processes is Avoided.
||You must not set this internal-use-only property to
||These properties affect election of a leader broker.
The leader broker sends a heartbeat to other brokers in the domain at intervals specified by the setting of the
If messages in the agent log indicate that leadership is not stable, you might want to adjust the settings of these properties according to the following rules:
While maintaining these rules, these adjustments might be helpful:
All timeout specifications are in milliseconds. For an understanding of the behavior specified by the settings of the
Also also About Brokers and Peering for more information about the leader broker.
Every update to the broker's durable domain configuration causes a Raft log entry. This property lets you set a maximum number of entries to be stored in the log. When the broker starts, it reads all log entries to compute the current set of state machines. This can get expensive if you have a large number of entries, which are also held in memory.
Note: Log compaction is configurable using
||For internal use only. Do not change the setting.|
name of this broker or agent's region. This property is useful for
Region distributed domains. The region of a host should not be changed
after it has been set. In general, the region name should reflect the
actual physical location of the host itself. For example,
||Use this property with the
||When set to
When set to
An alternative to using this host property is to invoke the NuoDB Manager
Not recommended for use in Production.
property specifies whether database processes (TEs, SMs, SSMs) can be started only through this broker or agent or can also be started
directly by starting a
When set to
|| The default behavior is that most domain events cause the enforcer to run, regardless of settings for
||This broker runs the enforcer every
When the enforcer runs, one of the results is an indication of whether this broker is the leader broker.
Every broker runs the enforcer according to this property setting. However, it is only the leader broker that does anything as a result of running the enforcer.
||After this broker starts, it runs the enforcer for the first time after
This property applies to all databases.
||For internal use only. You should not change the setting.|
||This property is not included in the
The default behavior is that reconnecting processes are already logged in the durable domain configuration because they would have been started by this broker.
Note: For information about the
propertyProvider property, see PropertiesProvider Plugin Class Customization.