Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-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 35C2B10BFF for ; Thu, 29 May 2014 15:10:57 +0000 (UTC) Received: (qmail 1153 invoked by uid 500); 29 May 2014 15:02:53 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 1025 invoked by uid 500); 29 May 2014 15:02:53 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 958 invoked by uid 99); 29 May 2014 15:02:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 May 2014 15:02:53 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of yuzhihong@gmail.com designates 209.85.213.52 as permitted sender) Received: from [209.85.213.52] (HELO mail-yh0-f52.google.com) (209.85.213.52) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 May 2014 15:02:50 +0000 Received: by mail-yh0-f52.google.com with SMTP id z6so370243yhz.39 for ; Thu, 29 May 2014 08:02:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Q4qD5hU2hq+G98aizESGgNZ66+4vSBY3py2IqUXXRvY=; b=Im5ZuiD5bCZXAJhhuq2hV+LitTZFFBivC5TRRXj1+dDL7mEbsTEog9mAJiOPJtqFO8 l7L0SJoaHscK4N4za/tFX1/YQMYe8tJdUQ+bRfSX43/yV3mHMont24T/vvtlmhJ+ht/U 41cAaLE9y1TOKUDc59wTc00df9VOb0SzUeEqpoX15VqlZLVatwkOdcbgrLOVDszsjpfv EICIFPxGHBo4uBamWTP9209BTZxV14nTs3HBCgXmnoBIYYQNCDHbrb1MycaO9oSaDuNL RW2Q1EdtkC+bZ52xDEK3EJ9mHZZjWVcy8zkra6VRoQWLtODKoupYP5Svq/b6zFrDDJol sFdA== MIME-Version: 1.0 X-Received: by 10.236.210.111 with SMTP id t75mr10850628yho.91.1401375746299; Thu, 29 May 2014 08:02:26 -0700 (PDT) Received: by 10.170.37.144 with HTTP; Thu, 29 May 2014 08:02:26 -0700 (PDT) In-Reply-To: <1401345461865-4059877.post@n3.nabble.com> References: <1401345461865-4059877.post@n3.nabble.com> Date: Thu, 29 May 2014 08:02:26 -0700 Message-ID: Subject: Re: Full stack rolling restart From: Ted Yu To: "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=089e0160a3f88e1f6a04fa8b3755 X-Virus-Checked: Checked by ClamAV on apache.org --089e0160a3f88e1f6a04fa8b3755 Content-Type: text/plain; charset=UTF-8 The following JIRAs may be of interest to you: HDFS-5535 HDFS-3867 Cheers On Wed, May 28, 2014 at 11:37 PM, sameerv wrote: > I am curious to know what the industry folks think of rolling restart on > the > full stack. Envisioning something like each node which services it runs, > stop all services, use new configs and start all services. Is it feasible > to > do this ? Can folks who have tried, share their experiences please? > > Thanks, > Sameer > > > > > -- > View this message in context: > http://apache-hbase.679495.n3.nabble.com/Full-stack-rolling-restart-tp4059877.html > Sent from the HBase User mailing list archive at Nabble.com. > --089e0160a3f88e1f6a04fa8b3755--