YAS3FS (Yet Another S3-backed File System) is a Filesystem in Userspace (FUSE) interface to Amazon S3. It was inspired by s3fs but rewritten from scratch to implement a distributed cache synchronized by Amazon SNS notifications. A web console is provided to easily monitor the nodes of a cluster.
I've observed this on 2.3.2. When a badly formatted SNS message is sent to a topic, all the yas3fs cluster nodes listening to that topic display a decode error.Then they stop listening to any future SNS messages until yas3fs is restarted.
This makes the notification services brittle. The more publishers to the SNS topic, the more probability of this happening. Specially if some of those are not yas3fs instances. (Lambda functions, etc)
I have not yet tested with the latest release but I will when I get time. I wanted to document this behavior first so I wouldn't forget about it though.
I've observed this on 2.3.2. When a badly formatted SNS message is sent to a topic, all the yas3fs cluster nodes listening to that topic display a decode error.Then they stop listening to any future SNS messages until yas3fs is restarted.
This makes the notification services brittle. The more publishers to the SNS topic, the more probability of this happening. Specially if some of those are not yas3fs instances. (Lambda functions, etc)
I have not yet tested with the latest release but I will when I get time. I wanted to document this behavior first so I wouldn't forget about it though.