Hi,
Recently, we hit an issue that, there is a difference between the freeSpace
of the datanode volume info and the OS df:
For example:
the jmx of the dn shows:
"VolumeInfo" :
"{\"/\":{\"freeSpace\":1445398864500,\"usedSpace\":228138206927,\"reservedSpace\":53687091200}}",
But the df shows
[
https://issues.apache.org/jira/browse/HDFS-12896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chencan resolved HDFS-12896.
Resolution: Duplicate
> when set replicate EC policy for a directory or file,it's EC policy cannot be
> que
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/652/
[Jan 9, 2018 11:09:33 AM] (sunilg) YARN-7718. DistributedShell failed to
specify resource other than
[Jan 9, 2018 12:27:01 PM] (bibinchundatt) YARN-7508. NPE in FiCaSchedulerApp
when debug log enabled in
[
Hajime Osako created HDFS-13005:
---
Summary: HttpFs checks subdirectories ACL status when LISTSTATUS
is used
Key: HDFS-13005
URL: https://issues.apache.org/jira/browse/HDFS-13005
Project: Hadoop HDFS
Hi, Andrew and Jason
Thanks for the feedback!
I will follow the pattern and cut the branch on Feb 1st and start the
RC vote around Feb 5th then.
Best
On Tue, Jan 9, 2018 at 11:35 AM, Jason Lowe wrote:
> Is it necessary to cut the branch so far ahead of the release? branch-3.0
> is already a m
Hi, Andrew and Jason
Thanks for the feedback!
I will follow the pattern and cut the branch on Feb 1st and start the
RC vote around Feb 5th then.
Best
On Tue, Jan 9, 2018 at 11:35 AM, Jason Lowe wrote:
> Is it necessary to cut the branch so far ahead of the release? branch-3.0
> is already a m
Is it necessary to cut the branch so far ahead of the release? branch-3.0
is already a maintenance line for 3.0.x releases. Is there a known
feature/improvement planned to go into branch-3.0 that is not desirable for
the 3.0.1 release?
I have found in the past that branching so early leads to ma
Hi Eddy, thanks for taking this on,
Historically we've waited for the first RC to cut the release branch since
it keeps things simpler for committers.
Also, could you check the permissions on your JIRA filter? It shows as
private for me.
Best,
Andrew
On Tue, Jan 9, 2018 at 11:17 AM, Lei Xu wro
Hi, All
We have released Apache Hadoop 3.0.0 in December [1]. To further
improve the quality of release, we plan to cut branch-3.0.1 branch
tomorrow for the preparation of Apache Hadoop 3.0.1 release. The focus
of 3.0.1 will be fixing blockers (3), critical bugs (1) and bug fixes
[2]. No new feat
Zsolt Venczel created HDFS-13004:
Summary: TestLeaseRecoveryStriped#testLeaseRecovery is failing
Key: HDFS-13004
URL: https://issues.apache.org/jira/browse/HDFS-13004
Project: Hadoop HDFS
Iss
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/651/
[Jan 8, 2018 9:20:17 PM] (billie) YARN-7704. Document improvement for registry
dns. Contributed by Jian He
[Jan 8, 2018 10:25:39 PM] (weiy) HDFS-12945. Switch to ClientProtocol instead
of NamenodeProtocols
Sreejith MV created HDFS-13003:
--
Summary: [OIV] Irrelevant access time for the dirs when run with
Delimited option
Key: HDFS-13003
URL: https://issues.apache.org/jira/browse/HDFS-13003
Project: Hadoop
Ranith Sardar created HDFS-13002:
Summary: Ulimit log is overridden by the balancer sysout log in
balancer out file
Key: HDFS-13002
URL: https://issues.apache.org/jira/browse/HDFS-13002
Project: Hadoo
Jianfei Jiang created HDFS-13001:
Summary: Testcase improvement for DFSAdmin
Key: HDFS-13001
URL: https://issues.apache.org/jira/browse/HDFS-13001
Project: Hadoop HDFS
Issue Type: Sub-task
Lokesh Jain created HDFS-13000:
--
Summary: Ozone: OzoneFileSystem: Implement seek functionality for
rest client
Key: HDFS-13000
URL: https://issues.apache.org/jira/browse/HDFS-13000
Project: Hadoop HDFS
15 matches
Mail list logo