-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Server Startup Setup
13416157913 edited this page May 12, 2023
·
2 revisions
This is a sample setup to run the services using Systemd.
It involves:
- Creating a service file (.service) in /etc/systemd/system/
- Enabling it
- Create the service file:
sudo nano /etc/systemd/system/seaweedmaster.service
- Insert the following text
[Unit]
Description=SeaweedFS Server
After=network.target
[Service]
Type=simple
User=root
Group=root
ExecStart=/usr/local/bin/weed master -ip=192.168.1.31
WorkingDirectory=/usr/local/bin
SyslogIdentifier=seaweedfs-master
[Install]
WantedBy=multi-user.target
- Start it and enable it
systemctl start seaweedmaster.service
systemctl enable seaweedmaster.service
- Create the service file:
sudo nano /etc/systemd/system/seaweedvolume.service
- Insert the following text
[Unit]
Description=SeaweedFS Volume
After=network.target media-jmn-LENOVO.mount
[Service]
Type=simple
User=root
Group=root
ExecStartPre=/bin/sleep 30
ExecStart=/usr/local/bin/weed volume -dir="/media/jmn/HDD/SeaweedFS"
WorkingDirectory=/usr/local/bin/
SyslogIdentifier=seaweedfs-volume
[Install]
WantedBy=multi-user.target
- Please, notice how I'm introducing a delay here for the mount to become available. Replace -dir= by your own directory for the Volume Server.:
- Also, please notice that I'm using "After" for the .mount file related with the directory I want the Volume Server to use. This won't be necessary if your data directory doesn't need to be mounted.
- Start it and enable it
systemctl start seaweedvolume.service
systemctl enable seaweedvolume.service
- Create the service file:
sudo nano /etc/systemd/system/seaweedfiler.service
- Insert the following text
[Unit]
Description=SeaweedFS Filer
After=network.target media-jmn-LENOVO.mount
[Service]
Type=simple
User=root
Group=root
ExecStartPre=/bin/sleep 30
ExecStart=/usr/local/bin/weed filer
WorkingDirectory=/media/jmn/HDD/
SyslogIdentifier=seaweedfs-filer
[Install]
WantedBy=multi-user.target
- Please, notice how I'm introducing a delay here for the mounted partition to become available.
- Also, please notice that I'm using "After" for the .mount file related with the directory I want the Filer to use. This won't be necessary if your data directory doesn't need to be mounted.
- Keep in mind that I'm setting the WorkingDirectory to a directory in my HDD and that has a filer.toml inside it with my desired configuration.
- Start it and enabled it
systemctl start seaweedfiler.service
systemctl enable seaweedfiler.service
- Replication
- Store file with a Time To Live
- Failover Master Server
- Erasure coding for warm storage
- Server Startup Setup
- Environment Variables
- Filer Setup
- Directories and Files
- Data Structure for Large Files
- Filer Data Encryption
- Filer Commands and Operations
- Filer JWT Use
- Filer Cassandra Setup
- Filer Redis Setup
- Filer YugabyteDB Setup
- Super Large Directories
- Path-Specific Filer Store
- Choosing a Filer Store
- Customize Filer Store
- Migrate to Filer Store
- Add New Filer Store
- Filer Store Replication
- Filer Active Active cross cluster continuous synchronization
- Filer as a Key-Large-Value Store
- Path Specific Configuration
- Filer Change Data Capture
- Cloud Drive Benefits
- Cloud Drive Architecture
- Configure Remote Storage
- Mount Remote Storage
- Cache Remote Storage
- Cloud Drive Quick Setup
- Gateway to Remote Object Storage
- Amazon S3 API
- AWS CLI with SeaweedFS
- s3cmd with SeaweedFS
- rclone with SeaweedFS
- restic with SeaweedFS
- nodejs with Seaweed S3
- S3 API Benchmark
- S3 API FAQ
- S3 Bucket Quota
- S3 API Audit log
- S3 Nginx Proxy
- Hadoop Compatible File System
- run Spark on SeaweedFS
- run HBase on SeaweedFS
- run Presto on SeaweedFS
- Hadoop Benchmark
- HDFS via S3 connector
- Async Replication to another Filer [Deprecated]
- Async Backup
- Async Filer Metadata Backup
- Async Replication to Cloud [Deprecated]
- Kubernetes Backups and Recovery with K8up