From user-return-60251-archive-asf-public=cust-asf.ponee.io@cassandra.apache.org Fri Mar 9 07:45:11 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id BF2D018064A for ; Fri, 9 Mar 2018 07:45:10 +0100 (CET) Received: (qmail 44430 invoked by uid 500); 9 Mar 2018 06:45:08 -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 44420 invoked by uid 99); 9 Mar 2018 06:45:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Mar 2018 06:45:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 6460F180376 for ; Fri, 9 Mar 2018 06:45:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.929 X-Spam-Level: X-Spam-Status: No, score=0.929 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id q_MZzkOd1Mx8 for ; Fri, 9 Mar 2018 06:45:06 +0000 (UTC) Received: from mail-pl0-f51.google.com (mail-pl0-f51.google.com [209.85.160.51]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 439E45F11F for ; Fri, 9 Mar 2018 06:45:05 +0000 (UTC) Received: by mail-pl0-f51.google.com with SMTP id i6-v6so4774928plt.7 for ; Thu, 08 Mar 2018 22:45:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=oh7ox6CIXtbwSS153QOuCu8lfuOvTdRpUNHgfjkMNiI=; b=E4a0XGuD3r0QGTgWstgGVT3JXgI8EL6e6+NHGYVK5GJbRHIqMoCkialo/44yJ9OYHt gjM6BgJK9vh3eV5UmjbnLTCfqsiq0nWFcG52pJyn9R1QsXU8vJdT2E6ulSr6mVYzuFO9 Es6LW5N8xBH8uSFVf6Lsk6ZxKG19D/MWURCDkvFhXJ7G/Vlt9HHNlxp0Y02p/LMrJNa3 6uUlcZrKLdBJp8x5s8JZovtsnFQoXpej/Nyrl9RHqKJAMNbg4mVGvM5fbLqVeu9G2mRt ij6RKpdYNzz1zOeV0vbv4vkKBs61FuYJ1jm8oBTP1Wk4HqK/HL9V5Or7QI1RPixMwkjX GDSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=oh7ox6CIXtbwSS153QOuCu8lfuOvTdRpUNHgfjkMNiI=; b=XIU401a+VhmIlLYtH+KhK4g1fn4CfqPD/ouTykIGhpyL9ad6EQqixIrSkDb5CdNhPG Sm9yRiR3fO2dFQYRLVweJpW5hVgyhQimkQDFuEDSyaAvXa/eTTcPxyLGJyaDY9FKrM/o +s3F3aO07qeyziArW5LoUJqgOpwM+JDoxHZgU5qwSytj4AMoJzCRWqjGvoHgSkdT14Lx 7eRt6TllOWt1szq/sv3W+7KVMcCxg5CXrcQRIZiYSiTOip73+vX9QEoz7TelTlSfLGvq vS79694Az9O1Y65SYIjponSLsc+KzxYJRkKhOiEm+ZdY454ohe5QzpwkuhAJV+ShumS1 SEmA== X-Gm-Message-State: APf1xPA+Df0NWKnEiSuILQJNs7zNuHxfSEG/ZHQsLTbyP/k3qvsAsfR9 uetdjDL46Pvd0iuh7FYquYL34r8e X-Google-Smtp-Source: AG47ELsBmFf1NuDwmhYstpr0G3xiyZeA8/vjViu4T/ynw2FFqhJvYHYRO1IMZnE8C+0IWcCobjFlKg== X-Received: by 2002:a17:902:28e3:: with SMTP id f90-v6mr26567297plb.355.1520577903168; Thu, 08 Mar 2018 22:45:03 -0800 (PST) Received: from [172.26.109.182] ([211.56.96.51]) by smtp.gmail.com with ESMTPSA id c62sm1307247pfk.127.2018.03.08.22.45.02 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 08 Mar 2018 22:45:02 -0800 (PST) From: Eunsu Kim Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Adding disk to operating C* Date: Fri, 9 Mar 2018 15:45:00 +0900 References: <749e6d88-df5f-44ab-854c-1baeedbed1ed@Spark> <7C962F21-34E1-4374-9E94-2BDBE9B5D2B3@gmail.com> <3893DCB1-7502-411A-81E6-BA0D5F0C9F2D@gmail.com> <5F083D0A-BB7D-4DAE-A707-B09AD5EA8E46@gmail.com> <15678E3F-6DA3-4FD1-99FB-23BA4B132ED5@gmail.com> To: user@cassandra.apache.org In-Reply-To: <15678E3F-6DA3-4FD1-99FB-23BA4B132ED5@gmail.com> Message-Id: <305D4846-64A8-445A-BF14-6328BFB89237@gmail.com> X-Mailer: Apple Mail (2.3445.5.20) Thanks for the answer. I never forget to flush, drain before shutting = down Cassandra. It is a system that deals with lighter and faster data than accuracy. So = rf =3D 2 and cl =3D one. Thank you again. > On 9 Mar 2018, at 3:12 PM, Jeff Jirsa wrote: >=20 > There is no shuffling as the servers go up and down. Cassandra = doesn=E2=80=99t do that.=20 >=20 > However, rf=3D2 is atypical and sometime problematic. >=20 > If you read or write with quorum / two / all, you=E2=80=99ll get = unavailables during the restart >=20 > If you read or write with cl one, you=E2=80=99ll potentially not see = data previously written (with or without the restart). >=20 > This is all just normal eventual consistency stuff, but be sure you = understand it - rf3 may be a better choice >=20 > On restart, be sure you shut down cleanly - nodetool flush and then = immediately nodetool drain. Beyond that I=E2=80=99d expect you to be = fine. >=20 > --=20 > Jeff Jirsa >=20 >=20 >> On Mar 8, 2018, at 9:52 PM, Eunsu Kim wrote: >>=20 >> There are currently 50000 writes per second. I was worried that the = server downtime would be quite long during disk mount operations. >> If the data shuffling that occurs when the server goes down or up is = working as expected, I seem to be an unnecessary concern. >>=20 >>=20 >>> On 9 Mar 2018, at 2:19 PM, Jeff Jirsa wrote: >>>=20 >>> I see no reason to believe you=E2=80=99d lose data doing this - why = do you suspect you may?=20 >>>=20 >>> --=20 >>> Jeff Jirsa >>>=20 >>>=20 >>>> On Mar 8, 2018, at 8:36 PM, Eunsu Kim = wrote: >>>>=20 >>>> The auto_snapshot setting is disabled. And the directory = architecture on the five nodes will match exactly. >>>>=20 >>>> (Cassandra/Server shutdown -> Mount disk -> Add directory to = data_file_directories -> Start Cassandra) * 5 rolling >>>>=20 >>>> Is it possible to add disks without losing data by doing the above = procedure? >>>>=20 >>>>=20 >>>>=20 >>>>> On 7 Mar 2018, at 7:59 PM, Rahul Singh = wrote: >>>>>=20 >>>>> Are you putting both the commitlogs and the Sstables on the adds? = Consider moving your snapshots often if that=E2=80=99s also taking up = space. Maybe able to save some space before you add drives. >>>>>=20 >>>>> You should be able to add these new drives and mount them without = an issue. Try to avoid different number of data dirs across nodes. It = makes automation of operational processes a little harder. >>>>>=20 >>>>> As an aside, Depending on your usecase you may not want to have a = data density over 1.5 TB per node. >>>>>=20 >>>>> -- >>>>> Rahul Singh >>>>> rahul.singh@anant.us >>>>>=20 >>>>> Anant Corporation >>>>>=20 >>>>>> On Mar 7, 2018, 1:26 AM -0500, Eunsu Kim = , wrote: >>>>>> Hello, >>>>>>=20 >>>>>> I use 5 nodes to create a cluster of Cassandra. (SSD 1TB) >>>>>>=20 >>>>>> I'm trying to mount an additional disk(SSD 1TB) on each node = because each disk usage growth rate is higher than I expected. Then I = will add the the directory to data_file_directories in cassanra.yaml >>>>>>=20 >>>>>> Can I get advice from who have experienced this situation? >>>>>> If we go through the above steps one by one, will we be able to = complete the upgrade without losing data? >>>>>> The replication strategy is SimpleStrategy, RF 2. >>>>>>=20 >>>>>> Thank you in advance >>>>>> = --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org >>>>>> For additional commands, e-mail: user-help@cassandra.apache.org >>>>>>=20 >>>>=20 >>>>=20 >>>> = --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org >>>> For additional commands, e-mail: user-help@cassandra.apache.org >>>>=20 >>>=20 >>> = --------------------------------------------------------------------- >>> To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org >>> For additional commands, e-mail: user-help@cassandra.apache.org >>>=20 >>=20 >>=20 >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org >> For additional commands, e-mail: user-help@cassandra.apache.org >>=20 >=20 > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org > For additional commands, e-mail: user-help@cassandra.apache.org >=20 --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org For additional commands, e-mail: user-help@cassandra.apache.org