Re: commit log on NFS volume

The Second exception states there is a File of an sstable Missing. Is it possible you didnt only delete commit logs or nfs Mount is stale or Not mounted? Am 01.11.2016 19:52 schrieb "John Sanda" : > Using nfs for a distribited System like Cassandra is like putting a >>

Re: commit log on NFS volume

> > Using nfs for a distribited System like Cassandra is like putting a > Ferrari on a Truck and going for a Race with the Truck. It is simply > nonsense. As I mentioned in my original post, I am aware that using NFS is considered bad and even documented as an anti-pattern. Your analogy,

Re: commit log on NFS volume

Using nfs for a distribited System like Cassandra is like putting a Ferrari on a Truck and going for a Race with the Truck. It is simply nonsense. Am 01.11.2016 19:39 schrieb "Vladimir Yudovin" : > Hi, > > it's not only performance issue. In case of network problem writer

Re: commit log on NFS volume

Hi, it's not only performance issue. In case of network problem writer tread can be blocked, also in case of failure loss of data can occur. Best regards, Vladimir Yudovin, Winguzone - Hosted Cloud Cassandra Launch your cluster in minutes. On Tue, 01 Nov 2016 14:10:10 -0400John

commit log on NFS volume

I know that using NFS is discouraged, particularly for the commit log. Can anyone shed some light into what kinds of problems I might encounter aside from performance? The reason for my inquiry is because I have some deployments with Cassandra 2.2.1 that use NFS and are experiencing some problems