Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of hadoophive@gmail.com
 designates 209.85.212.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <53D67DEE.6000806@ericsson.com>
References: <0N9F00JYYKMRH020@phonehome.asia.apple.com>
	<53D67DEE.6000806@ericsson.com>
Date: Mon, 28 Jul 2014 22:52:20 +0530
Message-ID: 
 <CADtHtMzm0Pjw3Q5CFj6igj08qeRiBRntjM-drv2cFDG+LP4G7w@mail.gmail.com>
Subject: Re: One datanode is down then write/read starts failing
From: hadoop hive <hadoophive@gmail.com>
To: user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=f46d043892b1576a4304ff442a97

--f46d043892b1576a4304ff442a97
Content-Type: text/plain; charset=UTF-8

If you have 2 an live initially and rep set to 2 which is perfectly fine
but you killed one dn... There is no place to put another replica of new
files as well as old files... Which causing issue in writing blocks.
On Jul 28, 2014 10:15 PM, "Satyam Singh" <satyam.singh@ericsson.com> wrote:

> @vikas i have initially set 2 but after that i have make one DN down. So
> you are saying from initial i have to make replication factor as 1 even i
> have DN 2 active initially. If so then what is the reason?
>
> On 07/28/2014 10:02 PM, Vikas Srivastava wrote:
>
>> What replication have you set for cluster.
>>
>> Its should be 1 in your case.
>>
>> On Jul 28, 2014 9:26 PM, Satyam Singh <satyam.singh@ericsson.com> wrote:
>>
>>> Hello,
>>>
>>>
>>> I have hadoop cluster setup of one namenode and two datanodes.
>>> And i continuously write/read/delete through hdfs on namenode through
>>> hadoop client.
>>>
>>> Then i kill one of the datanode, still one is working but writing on
>>> datanode is getting failed for all write requests.
>>>
>>> I want to overcome this scenario because at live traffic scenario any of
>>> datanode might get down then how do we handle those cases.
>>>
>>> Can anybody face this issue or i am doing something wrong in my setup.
>>>
>>> Thanx in advance.
>>>
>>>
>>> Warm Regards,
>>> Satyam
>>>
>>
>

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

<p dir=3D"ltr">If you have 2 an live initially and rep set to 2 which is pe=
rfectly fine but you killed one dn... There is no place to put another repl=
ica of new files as well as old files... Which causing issue in writing blo=
cks.</p>

<div class=3D"gmail_quote">On Jul 28, 2014 10:15 PM, &quot;Satyam Singh&quo=
t; &lt;<a href=3D"mailto:satyam.singh@ericsson.com">satyam.singh@ericsson.c=
om</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
@vikas i have initially set 2 but after that i have make one DN down. So yo=
u are saying from initial i have to make replication factor as 1 even i hav=
e DN 2 active initially. If so then what is the reason?<br>
<br>
On 07/28/2014 10:02 PM, Vikas Srivastava wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
What replication have you set for cluster.<br>
<br>
Its should be 1 in your case.<br>
<br>
On Jul 28, 2014 9:26 PM, Satyam Singh &lt;<a href=3D"mailto:satyam.singh@er=
icsson.com" target=3D"_blank">satyam.singh@ericsson.com</a>&gt; wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hello,<br>
<br>
<br>
I have hadoop cluster setup of one namenode and two datanodes.<br>
And i continuously write/read/delete through hdfs on namenode through<br>
hadoop client.<br>
<br>
Then i kill one of the datanode, still one is working but writing on<br>
datanode is getting failed for all write requests.<br>
<br>
I want to overcome this scenario because at live traffic scenario any of<br=
>
datanode might get down then how do we handle those cases.<br>
<br>
Can anybody face this issue or i am doing something wrong in my setup.<br>
<br>
Thanx in advance.<br>
<br>
<br>
Warm Regards,<br>
Satyam<br>
</blockquote></blockquote>
<br>
</blockquote></div>

--f46d043892b1576a4304ff442a97--