NFS gateway

2016-04-21 Thread Ranjith Raghunath
Is anyone successfully using HDFS as a fileshare?

RE: GSSException: Defective token detected

2015-10-09 Thread Ranjith Raghunath
:8088/cluster. > > > > *From:* Ranjith Raghunath [mailto:ranjith.raghuna...@gmail.com] > *Sent:* Friday, October 9, 2015 11:52 AM > *To:* user@hadoop.apache.org > *Subject:* RE: GSSException: Defective token detected > > > > Do any of the other UIs work? For example YARN applica

RE: GSSException: Defective token detected

2015-10-08 Thread Ranjith Raghunath
his url without any problems. > > > > *From:* Ranjith Raghunath [mailto:ranjith.raghuna...@gmail.com] > *Sent:* Friday, October 9, 2015 11:41 AM > *To:* user@hadoop.apache.org > *Cc:* jingfei...@hotmail.com > *Subject:* Re: GSSException: Defective token detected > > >

Re: GSSException: Defective token detected

2015-10-08 Thread Ranjith Raghunath
Are you using Firefox or chrome? Also, what webpage are you accessing (resource manager, namenode, etc.)? On Oct 8, 2015 10:20 PM, "Jingfei Hu" wrote: > *HTTP ERROR 403* > > Problem accessing /webhdfs/v1/. Reason: > > GSSException: Defective token detected (Mechanism level: GSSHeader did > no

Re: Replication

2012-10-30 Thread ranjith raghunath
sing namenode decides > the nodes in replication pipeline? > > On Tue, Oct 30, 2012 at 5:36 PM, ranjith raghunath < > ranjith.raghuna...@gmail.com> wrote: > >> If your client node is a datanode with your cluster then the first copy >> does get written to that data node

Re: Spindle per Cores

2012-10-12 Thread ranjith raghunath
.) > > Again YMMV and of course thanks to this guy Moore who decided to write > some weird laws... the ratio could change over time as the CPUs become more > efficient and faster. > > > On Oct 12, 2012, at 9:52 PM, ranjith raghunath < > ranjith.raghuna...@gmail.com> wrote:

Re: Spindle per Cores

2012-10-12 Thread ranjith raghunath
Does hypertheading affect this ratio? On Oct 12, 2012 9:36 PM, "Michael Segel" wrote: > First, the obvious caveat... YMMV > > Having said that. > > The key here is to take a look across the various jobs that you will run. > Some may be more CPU intensive, others more I/O intensive. > > If you mon