Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
MIME-Version: 1.0
In-Reply-To: <93A43A8C-7081-4E29-A40D-5C548DB9D9C4@gmail.com>
References: <93A43A8C-7081-4E29-A40D-5C548DB9D9C4@gmail.com>
From: daemeon reiydelle <daemeonr@gmail.com>
Date: Thu, 6 Jul 2017 09:29:13 -0700
Message-ID: <CAOUOv0EhDhRN5H0kCzqVSZ9Jw=uza15KVAS9+KhyCVpeJzQQow@mail.gmail.com>
Subject: Re: reconfiguring storage
To: Brian Jeltema <bdjeltema@gmail.com>
Cc: user <user@hadoop.apache.org>
Content-Type: multipart/alternative; boundary="94eb2c0e76fcc43c560553a89fed"
archived-at: Thu, 06 Jul 2017 16:29:49 -0000

--94eb2c0e76fcc43c560553a89fed
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Another option is to stop the node's relevant Hadoop services (including
e.g spark, impala, etc. if applicable), move the existing local storage,
mount the desired file system, and move the data over. Then just restart
hadoop. As long as this does not take too long, you don't have write
consistency that forces that shard to be written, etc. you will be fine.


*Daemeon C.M. ReiydelleUSA (+1) 415.501.0198London (+44) (0) 20 8144 9872*


On Thu, Jul 6, 2017 at 9:17 AM, Brian Jeltema <bdjeltema@gmail.com> wrote:

> I recently discovered that I made a mistake setting up some cluster nodes
> and didn=E2=80=99t
> attach storage to some mount points for HDFS. To fix this, I presume I
> should decommission
> the relevant nodes, fix the mounts, then recommission the nodes.
>
> My question is, when the nodes are recommissioned, will the HDFS storage
> automatically be reset to =E2=80=98empty=E2=80=99, or do I need to perfor=
m some sort of
> explicit
> initialization on those volumes before returning the nodes to active
> status.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: user-help@hadoop.apache.org
>
>

--94eb2c0e76fcc43c560553a89fed
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:comic sa=
ns ms,sans-serif;color:rgb(7,55,99)">Another option is to stop the node&#39=
;s relevant Hadoop services (including e.g spark, impala, etc. if applicabl=
e), move the existing local storage, mount the desired file system, and mov=
e the data over. Then just restart hadoop. As long as this does not take to=
o long, you don&#39;t have write consistency that forces that shard to be w=
ritten, etc. you will be fine.<br></div></div><div class=3D"gmail_extra"><b=
r clear=3D"all"><div><div class=3D"gmail_signature" data-smartmail=3D"gmail=
_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><d=
iv><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div d=
ir=3D"ltr"><span style=3D"color:rgb(56,118,29)"><span style=3D"background-c=
olor:rgb(255,255,255)"><b><span style=3D"font-family:comic sans ms,sans-ser=
if"></span></b></span></span><span style=3D"color:rgb(56,118,29)"><span sty=
le=3D"background-color:rgb(255,255,255)"><b><span style=3D"font-family:comi=
c sans ms,sans-serif"></span></b></span></span><span style=3D"color:rgb(56,=
118,29)"><span style=3D"background-color:rgb(255,255,255)"><b><span style=
=3D"font-family:comic sans ms,sans-serif"><span><font size=3D"1"><i><br></i=
></font></span></span></b></span></span><br><span style=3D"color:rgb(56,118=
,29)"><span style=3D"background-color:rgb(255,255,255)"><b><span style=3D"f=
ont-family:comic sans ms,sans-serif">Daemeon C.M. Reiydelle<br>USA (+1) 415=
.501.0198<br>London (+44) (0) 20 8144 9872</span></b></span></span><font si=
ze=3D"1"><i><br></i></font><span><span style=3D"color:rgb(56,118,29)"><span=
 style=3D"background-color:rgb(255,255,255)"><b><span style=3D"font-family:=
comic sans ms,sans-serif"><span><i><span><span style=3D"color:rgb(56,118,29=
)"><span style=3D"background-color:rgb(255,255,255)"><b><span style=3D"font=
-family:comic sans ms,sans-serif"><br></span></b></span></span></span></i><=
/span></span></b></span></span></span></div></div></div></div></div></div><=
/div></div></div></div></div></div></div></div></div>
<br><div class=3D"gmail_quote">On Thu, Jul 6, 2017 at 9:17 AM, Brian Jeltem=
a <span dir=3D"ltr">&lt;<a href=3D"mailto:bdjeltema@gmail.com" target=3D"_b=
lank">bdjeltema@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">I recently discovered that I made a mistake setting up some cluster =
nodes and didn=E2=80=99t<br>
attach storage to some mount points for HDFS. To fix this, I presume I shou=
ld decommission<br>
the relevant nodes, fix the mounts, then recommission the nodes.<br>
<br>
My question is, when the nodes are recommissioned, will the HDFS storage<br=
>
automatically be reset to =E2=80=98empty=E2=80=99, or do I need to perform =
some sort of explicit<br>
initialization on those volumes before returning the nodes to active status=
.<br>
------------------------------<wbr>------------------------------<wbr>-----=
----<br>
To unsubscribe, e-mail: <a href=3D"mailto:user-unsubscribe@hadoop.apache.or=
g">user-unsubscribe@hadoop.<wbr>apache.org</a><br>
For additional commands, e-mail: <a href=3D"mailto:user-help@hadoop.apache.=
org">user-help@hadoop.apache.org</a><br>
<br>
</blockquote></div><br></div>

--94eb2c0e76fcc43c560553a89fed--