DolphinDB ARM Standalone Deployment

• Official website: DolphinDB
• Or you can download DolphinDB for ARM with a shell command:

wget https://www.dolphindb.com/downloads/DolphinDB_ARM64_V${release}.zip -O dolphindb.zip

${release} refers to the version of DolphinDB server. For example, you can download ARM64 server 2.00.11.3 with the following command:

wget https://www.dolphindb.com/downloads/DolphinDB_ARM64_V2.00.11.3.zip -O dolphindb.zip

• Then extract the installation package to the specified directory (/path/to/directory):

unzip dolphindb.zip -d </path/to/directory>

Note: The directory name cannot contain any space characters, otherwise the startup of the data node will fail.

If you have obtained the Enterprise Edition license, use it to replace the following file:

/DolphinDB/server/dolphindb.lic

Otherwise, you can continue to use the community version of DolphinDB, which allows up to 8GB RAM use for 20 years.

Navigate to the folder /DolphinDB/server . The file permissions need to be modified for the first startup. Execute the following shell command:

chmod +x dolphindb

Due to the limited memory of the system, you need to modify the memory-related configuration parameters according to your device for the first startup. Execute the following shell command:

vim dolphindb.cfg

The default port number of the system is 8848. You can change it (e.g., to 8900) with the parameter localSite:

localSite=localhost:8900:local8900

Specify the maximum amount of memory (in GB) allocated to DolphinDB with parameter maxMemSize, e.g., to set it to 0.8 GB:

maxMemSize=0.8

Specify the maximum amount of memory (in MB) allocated to an array with parameter regularArrayMemoryLimit. It must be the exponential power of 2 with the default value of 512. To set it to 64 MB:

regularArrayMemoryLimit=64

Set the parameter maxLogSize. When the log file reaches the specified size it will be archived. The default value is 1024 MB and the minimum value is 100 MB. To set it to 100MB:

maxLogSize=100

• Linux console mode:

  ./dolphindb

• Linux background mode:

  sh startSingle.sh

To check whether the node was started, execute the following shell command:

ps aux|grep dolphindb

The following information indicates a successful startup:

Enter the deployment server IP address and port number (8848 by default) in the browser to navigate to the DolphinDB Web. The server address (ip:port) used in this tutorial is 10.0.0.82:8848. Below is the web interface.

Note: If the browser and DolphinDB are not deployed on the same server, you should turn off the firewall or open the corresponding port beforehand.

Navigate to the folder /DolphinDB/server/clusterDemo to execute the following command:

./stopAllNode.sh

The default directory to save the metadata for a standalone mode is:

/DolphinDB/server/local8848/dfsMeta/

/DolphinDB/server/local8848/storage/CHUNK_METADATA/

Back up the metadata with the following command:

mkdir backup
cp -r local8848/dfsMeta/ backup/dfsMeta
cp -r local8848/storage/CHUNK_METADATA/ backup/CHUNK_METADATA

Note: If the backup files are not in the above default directories, check the directories specified by the configuration parameters dfsMetaDir and chunkMetaDir. If the configuration parameters are not modified but the configuration parameter volumes is specified, then you can find the CHUNK_METADATA under the volumes directory.

Note: When the server is upgraded to a certain version, the plugin should also be upgraded to the corresponding version.

Download a new version of server package from DolphinDB website.

Replace the existing server with all files (except dolphindb.cfg and dolphindb.lic) in the current \DolphinDB\server folder.

Navigate to the folder /DolphinDB/server to start the server with the following command:

sh startSingle.sh

Open the web interface and execute the following script to check the current version of DolphinDB.

version()

Replace an existing license file with a new one.

License file path:

/DolphinDB/server/dolphindb.lic

• Online Update

  Execute the following script in web interface:

  updateLicense()

  Note:

  • The client name of the license cannot be changed.
  • The number of nodes, memory size, and the number of CPU cores cannot be smaller than the original license.
  • The update takes effect only on the node where the function is executed. Therefore, in a cluster mode, the function needs to be run on all controllers, agents, data nodes, and compute nodes.
  • The license type must be either commercial (paid) of free.

• Offline Update

  Restart DolphinDB server to complete the updates.