Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C5DCA1056C for ; Fri, 8 Nov 2013 18:31:58 +0000 (UTC) Received: (qmail 63574 invoked by uid 500); 8 Nov 2013 18:31:56 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 63517 invoked by uid 500); 8 Nov 2013 18:31:55 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 63509 invoked by uid 99); 8 Nov 2013 18:31:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Nov 2013 18:31:55 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of genericelias@gmail.com designates 209.85.219.48 as permitted sender) Received: from [209.85.219.48] (HELO mail-oa0-f48.google.com) (209.85.219.48) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Nov 2013 18:31:48 +0000 Received: by mail-oa0-f48.google.com with SMTP id h16so2746582oag.21 for ; Fri, 08 Nov 2013 10:31:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=DKv2A4qDPsP+2nOny8KUd+bmH/nkpTX5M80NzlR7guA=; b=rwx2iExQFEtkqRM042aGn7084xZZj5w8WcLogV/XMT2drDqlAxONN1OSmNMIXxmAL/ OPAAVB/YrkWMGZt69/lyPDoS4sO5BmOSLJgbiZzul+cyM0lmA3y+pEZB5P5prNaHaEdA iIQ0wwe/kKS+/A8IsRnFcH4WO9mfj/+oeXahTpfuFD1IRkWaYUfpEwuZZtXj4X58ZGGr +mHX98gCX4CVzJ9Q8CBkmzQVZRg5i11qGElPtiu0DMcRdXrMRCStv893NHGNzW6Qaq1t ZKdxJCzk124AqBDSSMI6QhKpaHxNpPRhjQW2PT7vVI19eVmKYU7gXM/9Q60I84zlw1P5 VrRg== MIME-Version: 1.0 X-Received: by 10.182.220.225 with SMTP id pz1mr2869776obc.51.1383935487417; Fri, 08 Nov 2013 10:31:27 -0800 (PST) Sender: genericelias@gmail.com Received: by 10.76.83.1 with HTTP; Fri, 8 Nov 2013 10:31:27 -0800 (PST) In-Reply-To: References: Date: Fri, 8 Nov 2013 10:31:27 -0800 X-Google-Sender-Auth: tDiMcSelG-WVzgYszeFa1xj2uqE Message-ID: Subject: Re: cleanup failure; FileNotFoundException deleting (wrong?) db file From: Elias Ross To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a11c30fac1eabb004eaae974d X-Virus-Checked: Checked by ClamAV on apache.org --001a11c30fac1eabb004eaae974d Content-Type: text/plain; charset=ISO-8859-1 On Thu, Nov 7, 2013 at 7:01 PM, Krishna Chaitanya wrote: > Check if its an issue with permissions or broken links.. > > I don't think permissions are an issue. You might be on to something regarding the links. I've been seeing this on 4 nodes, configured identically. Here's what I think the problem may be: (or may be a combination of a few problems) 1. I have symlinked the data directories. This confuses Cassandra in some way, causing it to create multiple files. Does Cassandra care if the data directory was symlinked from someplace? Would this cause an issue. lrwxrwxrwx 1 root root 6 Oct 30 18:37 data01 -> /data1 # [1] Evidence for: a. Somehow it's creating duplicate hard links. b. It is unlikely other Cassandra users would have setup their directories like this and this seems like a serious bug. c. Also, my other cluster is nearly identical (OS, JVM, 6 drives, same Cassandra/RHQ, hardware similar) and not seeing the same issues, although that is a two node cluster. If I were to grep through, I guess I would see if there's a chance the path that Java sees, maybe File.getAbsoluteFile() (which might resolve the link) doesn't match the path of another file. In other words, it is a Cassandra bug, based on some assumptions from the JVM 2. When I created the cluster, I had a single data directory for each node. I then added 5 more. Somehow Cassandra mis-remembers where the data was put, causing all sorts of issues. How does Cassandra decide where to put its data and where to read it from? What happens when additional data directories are added? There could be a bug in the code. Evidence for: a. Somehow it's looking for data in the wrong directory. It also seems unlikely a user would create a cluster, then add 5 more drives. # [1] The reason the links are setup is because the mount points didn't match my Puppet setup, which sets up my directory permissions. So I added the links to compensate. --001a11c30fac1eabb004eaae974d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Thu, Nov 7, 2013 at 7:01 PM, Krishna Chaitanya <b= nsk1990rulz@gmail.com> wrote:
<= div class=3D"gmail_quote">

Check if its an issue with permissions or broken links.= .



I don't think permissions are an issue. You might be on to somet= hing regarding the links.

I've been seeing thi= s on 4 nodes, configured identically.

Here's what I think the problem may be: (or may be = a combination of a few problems)

1. I have symlink= ed the data directories. This confuses Cassandra in some way, causing it to= create multiple files. Does Cassandra care if the data directory was symli= nked from someplace? Would this cause an issue.

lrwxrwxrwx =A0 =A01 root root =A0 =A0 6 Oct = 30 18:37 data01 -> /data1 # [1]

Evidence = for:
a. Somehow it's creating duplicate hard links.
b. It is unlikely other Cassandra users would have setup their directories= like this and this seems like a serious bug.
c. Also, my other cluster is nearly identical (OS, JVM, 6 drives, same= Cassandra/RHQ, hardware similar) and not seeing the same issues, although = that is a two node cluster.

If I were to = grep through, I guess I would see if there's a chance the path that Jav= a sees, maybe File.getAbsoluteFile() (which might resolve the link) doesn&#= 39;t match the path of another file. In other words, it is a Cassandra bug,= based on some assumptions from the JVM


2. When I created the cluster, I h= ad a single data directory for each node. I then added 5 more. Somehow Cass= andra mis-remembers where the data was put, causing all sorts of issues. Ho= w does Cassandra decide where to put its data and where to read it from? Wh= at happens when additional data directories are added? There could be a bug= in the code.

Evidence for:
a. Somehow it's looking for= data in the wrong directory. It also seems unlikely a user would create a = cluster, then add 5 more drives.

# [1] The rea= son the links are setup is because the mount points didn't match my Pup= pet setup, which sets up my directory permissions. So I added the links to = compensate.
--001a11c30fac1eabb004eaae974d--