Re: Forcing a file to update its length

Hi David! A FileSystem class is an abstraction for the file system. It doesn't make sense to do an hsync on a file system (should the file system sync all files currently open / just the user's etc.) . With appropriate flags maybe you can make it make sense, but we don't have that functionality.

Re: Forcing a file to update its length

I don't think it'd be safe for a reader to force an update of length at the replica locations directly. Only the writer would be perfectly aware of the DNs in use for the replicas and their states, and the precise count of bytes entirely flushed out of the local buffer. Thereby only the writer is

Forcing a file to update its length

I understand that, when writing to a file, I can force it to update its length on the namenode by using the following command: ((DFSOutputStream) imageWriter.getWrappedStream()).hsync(EnumSet.of(SyncFlag.UPDATE_LENGTH)); Is there a way to force the update without having to open a

RE: Forcing a file to update its length

I don’t see where I can pass the UPDATE_LENGTH flag to hflush. Should it be there? David Best Regards, David R Robison Senior Systems Engineer [cid:image004.png@01D19182.F24CA3E0] From: Harsh J [mailto:ha...@cloudera.com] Sent: Wednesday, August 9, 2017 3:01 PM To: David Robison

Stopping a Yarn container started by another app master

Hi, How can I stop a container that was started by a different application master (another app attempt) using NMClientAsync/NMClient? In Apex we enable KeepContainersAcrossApplicationAttempts, so if an application master fails, another application master may reconnect to already running

Re: Forcing a file to update its length

You are right, sorry I hadn't checked before stating that. The Jira at https://issues.apache.org/jira/browse/HDFS-4213 has some history around this. Looking over your question again, you may not really require the update length flag (a forced NameNode RPC) at every writer and also the hsync