Name | Modified | Size | Downloads / Week |
---|---|---|---|
Parent folder | |||
README.md | 2024-01-09 | 834 Bytes | |
v2.3.5 source code.tar.gz | 2024-01-09 | 1.7 MB | |
v2.3.5 source code.zip | 2024-01-09 | 1.8 MB | |
Totals: 3 Items | 3.5 MB | 0 |
CursusDB Cluster and Node Bundle Stable v2.3.5
đ˘ NO BREAKING CHANGES
âď¸ Adjustments âď¸
- [x] Node to catch SIGINT, SIGTERM, SIGKILL, SIGQUIT, and SIGABRT. If we don't catch usual signals you will not get persisted data to disk in all cases.
Testing:
Get your nodes PID
lsof -i :7682
kill -6 NODEPID
# is SIGABRTkill -3 NODEPID
# is SIGQUITkill -9 NODEPID
# is SIGKILLkill -15 NODEPID
# is SIGTERMkill -2 NODEPID
# is SIGINT
You need to start then kill, check client, start kill, check client. So I usually check my actual collection and documents. If say you killed and the node wasn't handling -9 then you would get no persisted data. If there is a signal missing please do let me know.
Node on these signals will persist data.