Rakesh R created HDFS-13808:
---
Summary: [SPS]: Remove unwanted FSNamesystem
#isFileOpenedForWrite() and #getFileInfo() function
Key: HDFS-13808
URL: https://issues.apache.org/jira/browse/HDFS-13808
Project:
Jack Fan created HDFS-13807:
---
Summary: Large overhead when seek and read only a small piece from
a file
Key: HDFS-13807
URL: https://issues.apache.org/jira/browse/HDFS-13807
Project: Hadoop HDFS
I
Includes these additional votings we got 5 binding votings, and 12
non-binding votings, we have many others like Bibin/Akhil gave offline
suggestions and testing results. Thanks everyone for your help!
I've done most of staging/pushing works for the 3.1.1 release. Given Apache
mirrors will take so
For more details, see https://builds.apache.org/job/hadoop-trunk-win/552/
[Aug 7, 2018 5:15:28 PM] (virajith) HDFS-13796. Allow verbosity of
InMemoryLevelDBAliasMapServer to be
[Aug 7, 2018 7:36:55 PM] (wangda) YARN-8629. Container cleanup fails while
trying to delete Cgroups. (Suma
[Aug 7, 2018
Thanks for reporting this issue. I have filed a JIRA to address this issue.
https://issues.apache.org/jira/browse/HDDS-341
>So, consider this as a report. IMHO, cutting an Ozone release prior to a
>Hadoop release ill-advised given the distribution impact and the requirements
>of the merge vote.
Anu Engineer created HDDS-341:
-
Summary: HDDS/Ozone bits are leaking into Hadoop release
Key: HDDS-341
URL: https://issues.apache.org/jira/browse/HDDS-341
Project: Hadoop Distributed Data Store
I
> On Aug 8, 2018, at 12:56 PM, Anu Engineer wrote:
>
>> Has anyone verified that a Hadoop release doesn't have _any_ of the extra
>> ozone bits that are sprinkled outside the maven modules?
> As far as I know that is the state, we have had multiple Hadoop releases
> after ozone has been merg
> Given that there are some Ozone components spread out past the core maven
> modules, is the plan to release a Hadoop Trunk + Ozone tar ball or is more
> work going to go into segregating the Ozone components prior to release?
The official release will be a source tarball, we intend to release a
Given that there are some Ozone components spread out past the core maven
modules, is the plan to release a Hadoop Trunk + Ozone tar ball or is more work
going to go into segregating the Ozone components prior to release? Has anyone
verified that a Hadoop release doesn't have _any_ of the extr
Mukul Kumar Singh created HDDS-340:
--
Summary: ContainerStateMachine#readStateMachinedata should read
from temporary chunk file if the data is not present as committed chunk
Key: HDDS-340
URL: https://issues.apach
[
https://issues.apache.org/jira/browse/HDDS-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shashikant Banerjee resolved HDDS-197.
--
Resolution: Fixed
Fixed in the current code with HDDS-173.
> DataNode should return Cont
Shashikant Banerjee created HDDS-339:
Summary: Add block length and blockId in PutKeyResponse
Key: HDDS-339
URL: https://issues.apache.org/jira/browse/HDDS-339
Project: Hadoop Distributed Data Stor
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/862/
[Aug 7, 2018 9:33:14 AM] (msingh) HDDS-230. ContainerStateMachine should
implement readStateMachineData
[Aug 7, 2018 10:39:53 AM] (msingh) HDDS-301. ozone command shell does not
contain subcommand to run o
Nilotpal Nandi created HDDS-338:
---
Summary: ozoneFS allows to create file key and directory key with
same keyname
Key: HDDS-338
URL: https://issues.apache.org/jira/browse/HDDS-338
Project: Hadoop Distrib
Nilotpal Nandi created HDDS-337:
---
Summary: keys created with key name having special
character/wildcard should not allowed
Key: HDDS-337
URL: https://issues.apache.org/jira/browse/HDDS-337
Project: Hado
Souryakanta Dwivedy created HDFS-13806:
--
Summary: EC: No error message for unsetting EC policy of the
directory inherits the erasure coding policy from an ancestor directory
Key: HDFS-13806
URL: https://issue
Surendra Singh Lilhore created HDFS-13805:
-
Summary: Journal Nodes should allow to format non-empty
directories with "-force" option
Key: HDFS-13805
URL: https://issues.apache.org/jira/browse/HDFS-13805
Elek, Marton created HDDS-336:
-
Summary: Print out container location information for a specific
ozone key
Key: HDDS-336
URL: https://issues.apache.org/jira/browse/HDDS-336
Project: Hadoop Distributed Da
maobaolong created HDFS-13804:
-
Summary: DN maxDataLength is useless except DN webui. I suggest to
get maxDataLength from NN heartbeat.
Key: HDFS-13804
URL: https://issues.apache.org/jira/browse/HDFS-13804
19 matches
Mail list logo