Managing Docker Storage and Load Balancing with Typesense Server
TLDR gaurav need help with Docker arguments for logs and planning for load balancing. Kishore Nallan suggested removal of space after parameters along with existence check of /logs directory and agreed with LB plan with independent instance setup.
Nov 01, 2022 (14 months ago)
gaurav
05:39 AMJust wanted to understand some arguments in docker.
1. When i run below command, still i couldnt see any data dir or log dir where i can see logs. I wanted to get all logs in a persistent storage.
sudo docker run -p 8108:8108 -v$(pwd)/typesense-data:/data typesense/typesense:0.23.1 --data-dir /data --log-dir= /logs --api-key=up_stox_ds --enable-cors2. Also i was planning to use LB with multiple VM for high availability instead of docker swarm just for reducing the complexity. I hops its fine.
Kishore Nallan
06:19 AM= ?--data-dir=/data --log-dir=/logsAnd ensure that
/logs exists.Kishore Nallan
06:20 AMgaurav
10:03 AM
Typesense
Indexed 3015 threads (79% resolved)
Similar Threads
Troubleshooting Typesense Server Error on Docker
vikram was facing an error with Typesense Server Docker container and loss of data on restart. Kishore Nallan guided to avoid mounting tmp directory from localhost and explained stopping the Docker container.
Running Typesense in Docker Container on Windows 10
Christian had issues running Typesense in Docker due to an unrecognized data directory. Jason suggested a solution to fix the file path issue, which Christian successfully implemented using Windows Powershell.
Trouble with Typesense Memory Usage when Restarting Docker Container
Blend reports increased memory usage when restarting Docker with Typesense, information shared with Jason and Kishore Nallan. Potential data edge case identified as potential cause, although resolution undetermined.