On Mon, Jan 31, 2011 at 1:57 PM, Konstantin Shvachko
wrote:
>
> Anybody with gcc active could you please verify if the problem is caused by
> HADOOP-6864.
>
I can build common trunk just fine on CentOS 5.5 including native.
I think the issue is somehow isolated to the build machines. Anyone know
Current trunk for HDFS and MapReduce are not compiling at the moment. Try to
build trunk.
This is the result of that changes to common api introduced by HADOOP-6904
are not promoted to HDFS and MR trunks.
HDFS-1335 and MAPREDUCE-2263 depend on these changes.
Common is not promoted to HDFS and MR b
The has been a problem with more than one build failing (Mahout is the one
that I saw first) due to a change in maven version which meant that the
clover license isn't being found properly. At least, that is the tale I
heard from infra.
On Mon, Jan 31, 2011 at 1:31 PM, Eli Collins wrote:
> Hey
Hey Konstantin,
The only build breakage I saw from HADOOP-6904 is MAPREDUCE-2290,
which was fixed. Trees from trunk are compiling against each other
for me (eg each installed to a local maven repo), perhaps the upstream
maven repo hasn't been updated with the latest bits yet.
Thanks,
Eli
On Mon
For those who wants to un-subscribe from certain Hadoop mailing lists
please follow
http://hadoop.apache.org/mapreduce/mailing_lists.html
--
Take care,
Konstantin (Cos) Boudnik
On Mon, Jan 31, 2011 at 12:51, Kang Jie wrote:
> On Mon, Jan 31, 2011 at 12:14 PM, Konstantin Shvachko
> wrote:
>
Sorry for the emails. Have been trying to move my email aliases arnd and
seem to be messing up!
Thanks
mahadev
On 1/31/11 12:51 PM, "Mahadev Konar" wrote:
> Unsubscribe.
>
>
Unsubscribe.
On Mon, Jan 31, 2011 at 12:14 PM, Konstantin Shvachko
wrote:
> Sending this to general to attract urgent attention.
> Both HDFS and MapReduce are not compiling since
> HADOOP-6904 and its hdfs and MP counterparts were committed.
> The problem is not with this patch as described below, but I think
Misspelled the subject line. Try sending again.
On Mon, Jan 31, 2011 at 3:48 PM, Mahadev Konar wrote:
> Unsubscribe.
>
>
Unsubscribe.
Sending this to general to attract urgent attention.
Both HDFS and MapReduce are not compiling since
HADOOP-6904 and its hdfs and MP counterparts were committed.
The problem is not with this patch as described below, but I think those
commits should be reversed if Common integration build cannot be
Well he didn't say he wanted to decommission the node, just stop it
independently of the name node. ;-)
-Original Message-
From: Koji Noguchi [mailto:knogu...@yahoo-inc.com]
Sent: Monday, January 31, 2011 11:16 AM
To: common-dev@hadoop.apache.org
Subject: Re: Stopping datanodes dynamical
If you want to decommission a datanode,
http://hadoop.apache.org/common/docs/r0.20.0/hdfs_user_guide.html#DFSAdmin+Command
-refreshNodes briefly explains how it works.
Koji
On 1/31/11 4:35 AM, "Segel, Mike" wrote:
James,
Remove the node without stopping what?
If you mean you want to remove
James,
Remove the node without stopping what?
If you mean you want to remove the data node without stopping the master, you
have a couple of ways...
First, if you're running Cloudera's CDH3b3 release you have /etc/init.d scripts
where you can issue a stop command.
(Stopping the datanode and th
Hi,
Can anyone please answer the question. How to remove the datanodes
dynamically from the masternode without stopping it?
15 matches
Mail list logo
