So is there a client program to call this?
Can one write their own simple client to call this method from all disks
on the cluster?
How about a map reduce job to collect from all disks on the cluster?
On 10/15/11 4:51 AM, "Uma Maheswara Rao G 72686"
wrote:
>/** Return the disk usage of the f
Hi Harsh,
I need access to the data programatically for system automation, and hence
I do not want a monitoring tool but access to the raw data.
I am more than happy to use an exposed function or client program and not
an internal API.
So i am still a bit confused... What is the simplest way to
Hi Harsh,
That brings up an interesting question i wanted to ask.
The connection between the data nodes and the name node is initiated by
the data node and not by the name node, based on the config file on the
data node machine.
Correct?
Cheers,
Ivan
On 10/17/11 9:28 PM, "Harsh J" wrote:
>He
Cool, is there any documentation on how to use the JMX stuff to get
monitoring data?
Cheers,
Ivan
On 10/17/11 6:04 PM, "Rajiv Chittajallu" wrote:
>If you are running > 0.20.204
>http://phanpy-nn1.hadoop.apache.org:50070/jmx?qry=Hadoop:service=NameNode,
>name=NameNodeInfo
>
>
>ivan.nov...@emc.co
Hello,
I am trying to understand how data locality works in hadoop.
If you run a map reduce job do the mappers only read data from the host on
which they are running?
Is there a communication protocol between the map reduce layer and HDFS layer
so that the mapper gets optimized to read data lo
So I guess the job tracker is the one reading the HDFS meta-data and then
optimizing the scheduling of map jobs based on that?
On 10/25/11 3:13 PM, "Shevek" wrote:
>We pray to $deity that the mapreduce block size is about the same as (or
>smaller than) the hdfs block size. We also pray that fil
Hello,
I am trying to automate formatting an HDFS volume. Is there any way to do this
without the interaction (and using expect)?
Cheers,
Ivan
Hi Raj and Arpit,
I think the fact that there are 2 confirmations is causing it not to work:
echo "Y" | hadoop namenode -format
11/09/22 14:57:10 INFO namenode.NameNode: STARTUP_MSG:
/
STARTUP_MSG: Starting NameNode
STARTUP_MSG: host =
Yeah I have a secondary namenode as well so 2 directories.
I was trying to avoid expect if possible. But this is always an option.
Cheers,
Ivan
On 9/22/11 3:17 PM, "Arpit Gupta" wrote:
>The reason you are getting multiple prompts is that you have multiple
>dir's defined in the dfs.name.dir
Hi Adam,
Well the "yes" program prints lower case y's and apparently only captial Y
is accepted.
But by creating my out "Yes" program that spews Y's to stdout it works :)
Cheers,
Ivan
On 9/22/11 3:02 PM, "Adam Shook" wrote:
>yes | hadoop namenode -format
>
>The "yes" program simply outputs 'y
Hi Harsh,
On 9/22/11 8:48 PM, "Harsh J" wrote:
>Ivan,
>
>Writing your own program was overkill.
>
>The 'yes' coreutil is pretty silly, but nifty at the same time. It
>accepts an argument, which it would repeat infinitely.
>
>So:
>
>$ yes Y | hadoop namenode -format
>
>Would do it for you.
Nice!
On 9/23/11 9:01 AM, "Edward Capriolo" wrote:
>On Fri, Sep 23, 2011 at 11:52 AM, wrote:
>
>> Hi Harsh,
>>
>> On 9/22/11 8:48 PM, "Harsh J" wrote:
>>
>> >Ivan,
>> >
>> >Writing your own program was overkill.
>> >
>> >The 'yes' coreutil is pretty silly, but nifty at the same time. It
>> >accepts
On 9/23/11 9:46 AM, "Harsh J" wrote:
>Ivan,
>
>On Fri, Sep 23, 2011 at 9:22 PM, wrote:
>[snip]
>> Which parameter are you referring to? I am planning on using 2
>>directories
>> in dfs.name.dir, one is local and the other is an NFS mount of a 2nd
>> machine running the secondary namenode.
>
>I'
13 matches
Mail list logo
