Server Picker
SQreamDB’s load balancer is called server_picker
.
Command Line Arguments
Parameters
Argument |
Default |
Description |
---|---|---|
|
|
The metadata server listening port |
|
|
The metadata server IP |
|
|
The server picker port |
|
|
The server picker ssl port |
|
|
The server picker log4 configuration file to use |
|
|
Refresh interval time to check available nodes |
|
None |
Lists services separated by comma |
|
None |
Used to display a help message or documentation for a particular program or command |
|
|
Configures the default location for the log file |
Example
server_picker --metadata_server_ip=127.0.0.1 --metadata_server_port=3105 --port=3118 --ssl_port=3119 --services=sqream23,sqream0 --log4_config=/home/sqream/metadata_log_properties --refresh_interval=10
Starting server picker
Starting temporarily
In general, you should not need to run server_picker
manually, but it is sometimes useful for testing.
Assuming we have a metadata server listening on the localhost, on port 3105:
nohup server_picker --metadata_server_ip=127.0.0.1 metadata_server_port=3105 &
SP_PID=$!
Using nohup
and &
sends server picker to run in the background.
Starting temporarily with non-default port
Tell server picker to listen on port 2255 for unsecured connections, and port 2266 for SSL connections.
nohup server_picker --metadata_server_ip=127.0.0.1 --metadata_server_port=3105 --port=2255 --ssl_port=2266 &
SP_PID=$!
Using nohup
and &
sends server picker to run in the background.
Stopping server picker
kill -9 $SP_PID
Tip
It is safe to stop any SQream DB component at any time using kill
. No partial data or data corruption should occur when using this method to stop the process.