| NowSMS - Cluster Nodes |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through June 03, 2020 ⬆ |
◄ ► |
| Author | Message | |||
| Jose Mosquera New member Username: Jmosquera Post Number: 7 Registered: 04-2019 |
Hello support wondering if you could help answer these questions: 1) How does a multi-node setup avoid duplicating a send if all nodes are reading from the same shared queue? 2) In the event of a node going down will others pick up SMS files that have been prefixed with the dead node's identifier? 3) What is the safest way to drain a node from the cluster to avoid data loss (inflight data, delivery messages received by another node)? 4) In our tests when loading up a cluster we see folders like these in the Q directory: 98876543210###0001 98876543210###0002 With roughly 45k sms msgs in each Is this just NowSMS managing the ingress of SMS msg across all nodes? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5999 Registered: 08-2008 |
1) Read/write file locking. 2) yes 3) normal shutdown / stop service / net stop nowsms 4) 45k seems very high. The default is 10k, but the logic for creating separate directories is simplistic and does not consider the same account name submitting high volume simultaneously. I would lower this limit as 45k files at a directory level will cause issues with most file systems. Our default behavior is to avoid placing more than 10000 files into a single directory, but the logic does not consider the same account name submitting high volume simultaneously, which is leading to higher counts. This setting can be adjusted with a MaxQDirEntries=#### entry under the [SMSGW] section of SMSGW.INI. I would suggest lowering to 2000 or even 1000. — Des NowSMS Support | |||
