Context
A client machine can get corrupted and send its corrupted data to Aerospike. Below are a few examples of log lines we’ve seen related to Aerospike receiving corrupted data:
May 27 2024 21:53:44 GMT: WARNING (service): (service.c:825) unsupported proto version 222 from 10.1.200.159:45972 May 27 2024 21:54:55 GMT: WARNING (rw): (write.c:1165) overwriting record in set 'set_1' but msg has different set name 'set_2' (8) 285ae543ed705dc23efca49b8a9a547875de5abc
“Unsupported proto version” means that there are messages of an unexpected type being sent to the main server port.
May 28 2024 01:18:49 GMT: WARNING (tsvc): (thr_tsvc.c:157) unknown namespace prob-13 (7) in protocol request - check configuration file
Given that our original namespace was “prof-13”, the logs are showing that there was a one-bit shift.