Yes!! So is there any locking mechanisms? Plus what dictates this delay in
file deletion and actual deletion of the file blocks over the cluster?
regards,
On Fri, Mar 14, 2008 at 6:22 AM, edward yoon <[EMAIL PROTECTED]> wrote:
> Can zookeeper locking services be used for these cases?
>
> Thanks
Can zookeeper locking services be used for these cases?
Thanks,
Edward.
On 3/13/08, Sanjay Radia <[EMAIL PROTECTED]> wrote:
> Ahmad Humayun wrote:
> > So does that mean nodes can possibly read files that have been "deleted"
> >
> If the name node entry has been deleted, new opens will fail.
> Alr
Ahmad Humayun wrote:
So does that mean nodes can possibly read files that have been "deleted"
If the name node entry has been deleted, new opens will fail.
Already opened files may have their reads succeed if they have cached
the block locations and also if the
blocks have not been deleted.
So does that mean nodes can possibly read files that have been "deleted"
thanks :)
regards,
On Wed, Mar 12, 2008 at 10:57 PM, Hairong Kuang <[EMAIL PROTECTED]>
wrote:
> > Case 1: Lets say there is a node which opens a file on the DFS to read.
> From
> > my understanding, the open request will
> Case 1: Lets say there is a node which opens a file on the DFS to read. From
> my understanding, the open request will go to the namenode, which will tell
> it where the blocks of the file are. What if another node comes up and asks
> to delete that file. Of course this request will go to the nam
Hi there,
I have some questions about the DFS functionality.
Case 1: Lets say there is a node which opens a file on the DFS to read. From
my understanding, the open request will go to the namenode, which will tell
it where the blocks of the file are. What if another node comes up and asks
to dele
