Re: VOTE: HDFS-347 merge

> We usually conclude the last VOTE before starting a new one. Otherwise, > people may be confused between the VOTEs. (In case you don't know our > convention. Please check with someone before starting a VOTE. Thanks.) > > > -1 > * The previous VOTE started by Colin has not been concluded. > N

Re: VOTE: HDFS-347 merge

On Thu, Apr 4, 2013 at 9:11 PM, Tsz Wo Sze wrote: > Colin, > > We usually conclude the last VOTE before starting a new one. Otherwise, > people may be confused between the VOTEs. (In case you don't know our > convention. Please check with someone before starting a VOTE. Thanks.) > > > -1 > *

Re: VOTE: HDFS-347 merge

Colin, We usually conclude the last VOTE before starting a new one.  Otherwise, people may be confused between the VOTEs.  (In case you don't know our convention.  Please check with someone before starting a VOTE.  Thanks.) -1 * The previous VOTE started by Colin has not been concluded. * The

[jira] [Resolved] (HDFS-4647) llegalStateException renaming file under snapshottable directory

[ https://issues.apache.org/jira/browse/HDFS-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE resolved HDFS-4647. -- Resolution: Fixed Hadoop Flags: Reviewed I have committed this. Thanks, A

Re: Max DataXceiver Exceeded Logs in DataNode log files

Hello Sreekanth, The threads that you see named "PacketResponder" are in fact the threads allocated from the BlockReceiver class. As you noticed, they are placed into the same thread group as the threads named "DataXceiver" allocated from the DataXceiverServer class. The current count is determi

Hadoop-Hdfs-trunk - Build # 1363 - Still Failing

See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1363/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 14194 lines...] Tests run: 16, Failures: 0, Errors: 0, Sk

Build failed in Jenkins: Hadoop-Hdfs-trunk #1363

See Changes: [llu] HDFS-4665. Move TestNetworkTopologyWithNodeGroup to common. (Junping Du via llu) [llu] HADOOP-9451. Fault single-layer config if node group topology is enabled. (Junping Du via llu) [vinodkv] YARN-536. Removed t

Jenkins build is still unstable: Hadoop-Hdfs-0.23-Build #572

See

Hadoop-Hdfs-0.23-Build - Build # 572 - Still Unstable

See https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/572/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 11947 lines...] [INFO] No dependencies found. [INFO]

Min Long is out of the office.

I will be out of the office starting 2013/04/04 and will not return until 2013/04/07. For urgent defects and items, please contact my manager or call pager. I will respond to non-urgent mails on 04/07. Thanks.

Fwd: Max DataXceiver Exceeded Logs in DataNode log files

Posting my previous mail from issues mailing list to dev mailing list. Hi All, We are currently running Hadoop 0.20.X version of hadoop cluster in our environment. We have been recently observing slow down of datanodes and DFSClient times out. Looking at the logs in the data nodes we noticed t

Re: On disk layout of HDFS...

1804 looks promising for the longer term. But yes, I suspect a rebalancer would be useful. I'll work on an offline one first. Kevin On Thu, Apr 4, 2013 at 10:45 AM, Harsh J wrote: > If you're looking for the online solution, Aaron's just posted a > working implementation of it at > https://issue

Re: On disk layout of HDFS...

If you're looking for the online solution, Aaron's just posted a working implementation of it at https://issues.apache.org/jira/browse/HDFS-1804. For the offline or asynchronous disk balancer discussed by https://issues.apache.org/jira/browse/HDFS-1312, if you want your tool to be part of the upst

Re: ReplicationTargetChooser has incorrect block placement comments

Hi Mei, Thanks. Please also keep hdfs-dev@hadoop.apache.org on the to: list when replying, so your questions get exposure from other HDFS devs as well :) Regarding your question, the answer is no, the NN will never violate the block placement policy on its own when choosing block location targets

Re: What do ns_quota and ds_quota mean in an namednode entry

name space, disk space. ns means block numbers limits. ds is total file size limitation. On Apr 4, 2013 3:12 PM, "Bert Yuan" wrote: > Bellow is json format of an namednode entry: > { > inode:{ > inodepath:'/anotherDir/biggerfile', > replication:3, > modificationtime:'2

[jira] [Resolved] (HDFS-4665) Move TestNetworkTopologyWithNodeGroup to Common

[ https://issues.apache.org/jira/browse/HDFS-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Lu resolved HDFS-4665. --- Resolution: Fixed Fix Version/s: 3.0.0 +1. Committed to trunk. Thanks Junping! > Move

Re: ReplicationTargetChooser has incorrect block placement comments

Good to know! Please also consider improving the javadoc on that method to reflect this, by logging a doc JIRA under HDFS :) On Thu, Apr 4, 2013 at 12:33 PM, Mei Long wrote: > Harsh, > > Thank you! This is exactly what I was confused about. By looking at the code > I was suspecting that it's not