Turning Off Typesense Server Logs
TLDR Manish inquired about turning off verbose Typesense server logs. Jason explained that the logs cannot be turned off due to their usefulness in debugging issues. There is no way to limit logs to warning level or above currently.
May 25, 2023 (4 months ago)
> I20230525 20:20:00.660845 262 raft_server.cpp:546] Term: 126, last_index index: 756, committed_index: 756, known_applied_index: 756, applying_index: 0, queued_writes: 0, pending_queue_size: 0, local_sequence: 1912
> I20230525 20:20:00.660920 288 raft_server.h:60] Peer refresh succeeded!
Is there a way to turn these off?
More context here: https://github.com/typesense/typesense/issues/475#issuecomment-1301621061
Indexed 2776 threads (79% resolved)
Discussion About Typesense Nodes Not Synchronizing Correctly
Erick experienced an issue where documents weren't updated properly in a Typesense instance running on 3 nodes. Upon requesting debug logs and configs, Jason identified that these nodes weren't part of the same cluster. They couldn't resolve the nodes' failure to connect issue and recommended a fresh installation.
Resolving Server Stoppage Issues in Typesense Multi VM Cluster
gaurav faced issues with the Typesense server in a multi VM cluster, including automatic stoppage and errors. Kishore Nallan identified the lack of a quorum and suggested using three nodes. When the issue persisted, they advised running Typesense via `nohup` or `systemd` to prevent session closure from stopping the process.
Addressing High CPU Usage in Typesense
Robert reported high CPU usage on Typesense, even after halting all incoming searches. Kishore Nallan suggested logging heavy queries and increasing thread count. The issue was resolved after Robert found and truncated unusually large documents in the database.