Many times while starting hadoop, bin/start-all.sh, I get this error
in logs/hadoop-root-namenode-master.log
/
STARTUP_MSG: Starting NameNode
STARTUP_MSG: host = master/127.0.0.1
STARTUP_MSG: args = []
I will see if I can replicate the problem and do as you suggest.
On 2/8/08 4:29 PM, "Raghu Angadi" <[EMAIL PROTECTED]> wrote:
> Ted Dunning wrote:
>> That makes it wait, but I don't think it increases the urgency on the part
>> of the namenode.
>>
>> As an interesting experiment, I had a clus
Ted Dunning wrote:
That makes it wait, but I don't think it increases the urgency on the part
of the namenode.
As an interesting experiment, I had a cluster with lots of pending
replication to do that was happening slowly. Restarting the name node
caused the rate of replication to increase mass
Release 0.16.0 contains many improvements, new features, bug fixes
and optimizations.
For release details and downloads, visit:
http://hadoop.apache.org/core/releases.html
Thanks to all who contributed to this release!
Nigel
That makes it wait, but I don't think it increases the urgency on the part
of the namenode.
As an interesting experiment, I had a cluster with lots of pending
replication to do that was happening slowly. Restarting the name node
caused the rate of replication to increase massively. The differen
On 2/8/08 9:32 AM, "Jeff Eastman" <[EMAIL PROTECTED]> wrote:
> I noticed that phenomena right off the bat. Is that a designed "feature"
> or just an unhappy consequence of how blocks are allocated?
My understanding is that this is by design--when you are running a MR
job, you want the output,
It doesn't happen immediately. It happens SLOWLY.
On 2/7/08 11:05 PM, "Tim Wintle" <[EMAIL PROTECTED]> wrote:
> Doesn't the -setrep command force the replication to be increased
> immediately?
>
> ./hadoop dfs -setrep [replication] path
>
> (I may have misunderstood)
>
>
> On Thu, 2008-02-
I noticed that phenomena right off the bat. Is that a designed "feature"
or just an unhappy consequence of how blocks are allocated? Ted
compensates for this by aggressively rebalancing his cluster often by
adjusting the replication up and down, but I wonder if an improvement in
the allocation stra
On 2/7/08 11:01 PM, "Tim Wintle" <[EMAIL PROTECTED]> wrote:
> it's
> useful to be able to connect from nodes that aren't in the slaves file
> so that you can put in input data direct from another machine that's not
> part of the cluster,
I'd actually recommend this as a best practice. We've
I have a Hadoop running on a master node 192.168.1.8. fs.default.name
is 192.168.101.8:9000 and mapred.job.tracker is 192.168.101.8:9001.
I am accessing it's web pages on port 50030 from another machine. I
visited http://192.168.101.8:50030/machines.jsp. It showed:-
NameHost# running task
it would help if u could paste ur output key comparator. it should override the
other things listed in ur mail - but the thing to watch out is that one has to
define both the compare(byte [] ...) and the compare(WritableComparable ...)
functions. i am wondering whether one was omitted .. (and in
Hi,
I am using a mini-cluster of three machines and on them experimented
with severel different (sometimes strrange) reduce settings (from one
single reduce per machine to 10 per machine).
...and the result is (basically) always the same, .i.e. the process gets
stucked (or at least very slow)
Hi guys,
I was wondering if someone could explain the possible interaction
effects between the different methods available to control key sorting.
Based on my understanding, there are three separate knobs:
- a WritableComparable's compareTo method
- registering a WritableComparator optimizat
there was a join operator on pre-sorted inputs that someone was working on ..
-Original Message-
From: Jason Venner [mailto:[EMAIL PROTECTED]
Sent: Thu 2/7/2008 8:51 PM
To: [EMAIL PROTECTED]
Subject: Question about joining two map sequence files - 0.15.3
Is there a smart way to find the
14 matches
Mail list logo
