Hi,
On Thu, Oct 14, 2010 at 10:59 PM, He Chen wrote:
> they arrived in 1 minute. I understand there will be a setup phase which
> will use any free slot no matter map or reduce.
>
You mean all jobs were submitted within a minute ? That means a few
seconds between jobs ? Or do you mean each job w
On Oct 14, 2010, at 12:58 PM, Null Ecksor wrote:
> Does the namenode starts a fresh and gather all the namespace information
> again from the datanodes?
>
> I want to know if at all it looses the info written on the disk, is it able
> to obtain the same from the datanodes in the cluster.
I've ad
Hi,
I have a small doubt regarding Hadoop. For a cluster without secondary
namenode, a namenode reboots itself after failure.
For a scenario,when a namenode reboots itself, and looses all the namespace
information--
Does the namenode starts a fresh and gather all the namespace information
again f
On Thu, Oct 14, 2010 at 03:44PM, Steve Loughran wrote:
> >On the other hand, there's a fairly large number of cases where no
> >introspection into daemons' internals is required. These can be carried by
> >a simple communication via Hadoop CLI. To name a few: testing ACL refreshes,
> >basic file op
[
https://issues.apache.org/jira/browse/HADOOP-6628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-6628.
--
Resolution: Fixed
> Make Cloudera commit logs and Yahoo! change logs into web-readable
Allow configuration changes without restarting configured nodes
---
Key: HADOOP-7001
URL: https://issues.apache.org/jira/browse/HADOOP-7001
Project: Hadoop Common
Issue Type: Task
I doubt this. According to the execution record. the disk and network
utilization are the same.
At last, if the FCFS scheduler only apply for the setup stage which takes
about several second. This does not mean anything. users who submit their
jobs earlier only ge job setup earlier, but may be del
Hi, Chen
I think it's due to the disk/network performance, I mean the speed of
reading the content on disk/network into the local memory
if job3 hasn't complete data to start mappers, but job4 does, the scheduler
would select the tasks of job4 from the list to run firstly,
I think the so called
they arrived in 1 minute. I understand there will be a setup phase which
will use any free slot no matter map or reduce.
My queue time is the period between the start of Map stage and the time job
is submitted. Because the setup phase has the higher priority than map and
reduce tasks. Any job subm
What is the inter-arrival time between these jobs?
There is a "set up" phase for jobs before they are launched. It is
possible that the order of jobs can change due to slightly different
set up times. Apart from the number of blocks, it may matter "where"
these blocks lie.
Abhishek
On Thu, Oct 1
Hi all
I am testing the performance of my Hadoop clsuters with Hadoop Default FIFO
schedular. But I find a interesting phenomina.
When I submit a series of jobs, some job will be executed earlier even they
are submitted late. All jobs are request same amount of blocks. For example:
job 1 submit
[
https://issues.apache.org/jira/browse/HADOOP-6992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting resolved HADOOP-6992.
--
Resolution: Fixed
Hadoop Flags: [Reviewed]
Hive has now moved its website, so I have now
On 08/10/10 22:06, Konstantin Boudnik wrote:
All,
I want to start a discussion about future approaches to perform Hadoop
system (and potentially other types of) testing in 0.22 and later.
As many of you know recent development effort from a number of Hadoop
developers brought to the existence n
13 matches
Mail list logo
