Apache Hadoop Ozone 0.4.1 (Biscayne) release plan
Hello Ozone committers, For Biscayne release, I have cut ozone-0.4.1 branch from trunk and updated "Fix Version/s" for existing resolved jiras accordingly. If you want to include any other jira(s) in this release, please update the "Target Version/s" of the jira(s) and use ozone-0.4.1 branch while committing. I will send out a follow-up mail on the code freeze date. Thanks, Nanda
[VOTE] Release Apache Hadoop Ozone 0.4.1-alpha
Hi Folks, I have put together RC0 for Apache Hadoop Ozone 0.4.1-alpha. The artifacts are at: https://home.apache.org/~nanda/ozone/release/0.4.1/RC0/ The maven artifacts are staged at: https://repository.apache.org/content/repositories/orgapachehadoop-1238/ The RC tag in git is at: https://github.com/apache/hadoop/tree/ozone-0.4.1-alpha-RC0 And the public key used for signing the artifacts can be found at: https://dist.apache.org/repos/dist/release/hadoop/common/KEYS This release contains 363 fixes/improvements [1]. Thanks to everyone who put in the effort to make this happen. *The vote will run for 7 days, ending on October 11th at 11:59 pm IST.* Note: This release is alpha quality, it’s not recommended to use in production but we believe that it’s stable enough to try out the feature set and collect feedback. [1] https://s.apache.org/yfudc Thanks, Team Ozone
[ANNOUNCE] Apache Hadoop Ozone 0.4.1-alpha release
Hello everyone, It gives us great pleasure to announce that the Apache Hadoop community has voted to release Apache Hadoop Ozone 0.4.1-alpha. Apache Hadoop Ozone is an object store for Hadoop built using Hadoop Distributed Data Store. For more information and to download, please check https://hadoop.apache.org/ozone Note: This release is alpha quality, it's not recommended to use in production. Thanks to everyone who put in the effort to make this happen. Cheers, Team Ozone
[jira] [Created] (HADOOP-16534) Exclude submarine code from hadoop source build
Nanda kumar created HADOOP-16534: Summary: Exclude submarine code from hadoop source build Key: HADOOP-16534 URL: https://issues.apache.org/jira/browse/HADOOP-16534 Project: Hadoop Common Issue Type: Bug Reporter: Nanda kumar Assignee: Nanda kumar When we do source package of hadoop, it should not contain submarine project/code. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-15152) Typo in javadoc of ReconfigurableBase#reconfigurePropertyImpl
Nanda kumar created HADOOP-15152:
Summary: Typo in javadoc of
ReconfigurableBase#reconfigurePropertyImpl
Key: HADOOP-15152
URL: https://issues.apache.org/jira/browse/HADOOP-15152
Project: Hadoop Common
Issue Type: Bug
Components: common
Reporter: Nanda kumar
Assignee: Nanda kumar
Priority: Trivial
There is a typo in javadoc of ReconfigurableBase#reconfigurePropertyImpl
{code}
* Subclasses must override this. This method applies the change to
* all internal data structures derived from the configuration property
* that is being changed. If this object owns other Reconfigurable objects
* reconfigureProperty should be called recursively to make sure that
* to make sure that the configuration of these objects is updated.
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-15255) Upper/Lower case conversion support for group names in LdapGroupsMapping
Nanda kumar created HADOOP-15255:
Summary: Upper/Lower case conversion support for group names in
LdapGroupsMapping
Key: HADOOP-15255
URL: https://issues.apache.org/jira/browse/HADOOP-15255
Project: Hadoop Common
Issue Type: Improvement
Reporter: Nanda kumar
On most LDAP servers the user and group names are case-insensitive. When we use
{{JniBasedUnixGroupsMappingWithFallback}} and have {{SSSD}} in place, it is
possible to configure {{SSSD}} to force the group names to be returned in
lowercase. If we use {{LdapGroupsMapping}}, we don't have any such option.
This jira proposes to introduce a new {{hadoop.security.group.mapping}}
implementation based on LdapGroupsMapping which supports force lower/upper case
group names.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-15266) [branch-2] Upper/Lower case conversion support for group names in LdapGroupsMapping
Nanda kumar created HADOOP-15266:
Summary: [branch-2] Upper/Lower case conversion support for group
names in LdapGroupsMapping
Key: HADOOP-15266
URL: https://issues.apache.org/jira/browse/HADOOP-15266
Project: Hadoop Common
Issue Type: Improvement
Reporter: Nanda kumar
Assignee: Nanda kumar
Fix For: 3.1.0
On most LDAP servers the user and group names are case-insensitive. When we use
{{JniBasedUnixGroupsMappingWithFallback}} and have {{SSSD}} in place, it is
possible to configure {{SSSD}} to force the group names to be returned in
lowercase. If we use {{LdapGroupsMapping}}, we don't have any such option.
This jira proposes to introduce a new {{hadoop.security.group.mapping}}
implementation based on LdapGroupsMapping which supports force lower/upper case
group names.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-15275) Incorrect javadoc in return type of RetryPolicy#shouldRetry
Nanda kumar created HADOOP-15275:
Summary: Incorrect javadoc in return type of
RetryPolicy#shouldRetry
Key: HADOOP-15275
URL: https://issues.apache.org/jira/browse/HADOOP-15275
Project: Hadoop Common
Issue Type: Bug
Reporter: Nanda kumar
Assignee: Nanda kumar
The return type of {{RetryPolicy#shouldRetry}} has been changed from
{{boolean}} to {{RetryAction}}, but the javadoc is not updated.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-15474) Rename properties introduced for
Nanda kumar created HADOOP-15474:
Summary: Rename properties introduced for
Key: HADOOP-15474
URL: https://issues.apache.org/jira/browse/HADOOP-15474
Project: Hadoop Common
Issue Type: Bug
Components: conf
Affects Versions: 3.1.0
Reporter: Nanda kumar
HADOOP-15007 introduces the following two properties for tagging configuration
properties
* hadoop.system.tags
* hadoop.custom.tags
This sounds like {{tags}} fall under {{hadoop.system}} and {{hadoop.custom}}
related properties, but what we really want to achieve here is to have two
sub-division of {{tags}} namely {{system}} and {{custom}}
For better readability, we can rename them as
* hadoop.tags.system
* hadoop.tags.custom
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-15486) Make NetworkTopology#netLock fair
Nanda kumar created HADOOP-15486:
Summary: Make NetworkTopology#netLock fair
Key: HADOOP-15486
URL: https://issues.apache.org/jira/browse/HADOOP-15486
Project: Hadoop Common
Issue Type: Improvement
Components: net
Reporter: Nanda kumar
Assignee: Nanda kumar
Whenever a datanode is restarted, the registration call after the restart
received by NameNode lands in {{NetworkTopology#add}} via
{{DatanodeManager#registerDatanode}} requires write lock on
{{NetworkTopology#netLock}}. This registration thread is getting starved by
flood of {{FSNamesystem.getAdditionalDatanode}} calls, which are triggered by
clients those who were writing to the restarted datanode.
The registration call which is waiting for write lock on
{{NetworkTopology#netLock}} is holding write lock on {{FSNamesystem#fsLock}},
causing all the other RPC calls which require the lock on
{{FSNamesystem#fsLock}} wait.
We can make {{NetworkTopology#netLock}} lock fair so that the registration
thread will not starve.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-15490) Multiple declaration of maven-enforcer-plugin found in pom.xml
Nanda kumar created HADOOP-15490:
Summary: Multiple declaration of maven-enforcer-plugin found in
pom.xml
Key: HADOOP-15490
URL: https://issues.apache.org/jira/browse/HADOOP-15490
Project: Hadoop Common
Issue Type: Bug
Reporter: Nanda kumar
Assignee: Nanda kumar
Multiple declaration of {{maven-enforcer-plugin}} in {{pom.xml}} is causing the
below warning during build.
{noformat}
[WARNING] Some problems were encountered while building the effective model for
org.apache.hadoop:hadoop-project:pom:3.2.0-SNAPSHOT
[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found
duplicate declaration of plugin org.apache.maven.plugins:maven-enforcer-plugin
@ org.apache.hadoop:hadoop-main:3.2.0-SNAPSHOT,
/Users/nvadivelu/codebase/apache/hadoop/pom.xml, line 431, column 15
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.hadoop:hadoop-main:pom:3.2.0-SNAPSHOT
[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found
duplicate declaration of plugin org.apache.maven.plugins:maven-enforcer-plugin
@ line 431, column 15
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-15526) Remove jdiff-workaround.patch from hadoop-common-project
Nanda kumar created HADOOP-15526:
Summary: Remove jdiff-workaround.patch from hadoop-common-project
Key: HADOOP-15526
URL: https://issues.apache.org/jira/browse/HADOOP-15526
Project: Hadoop Common
Issue Type: Bug
Components: common
Reporter: Nanda kumar
Assignee: Nanda kumar
Remove {{jdiff-workaround.patch}} file from codebase which is checked-in as
part of HADOOP-13428.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-15526) Remove jdiff-workaround.patch from hadoop-common-project
[
https://issues.apache.org/jira/browse/HADOOP-15526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nanda kumar resolved HADOOP-15526.
--
Resolution: Not A Problem
Assignee: (was: Nanda kumar)
> Remove jdiff-workaround.patch from hadoop-common-project
>
>
> Key: HADOOP-15526
> URL: https://issues.apache.org/jira/browse/HADOOP-15526
> Project: Hadoop Common
> Issue Type: Bug
> Components: common
> Reporter: Nanda kumar
>Priority: Trivial
>
> Remove {{jdiff-workaround.patch}} file from codebase which is checked-in as
> part of HADOOP-13428.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-7050) proxyuser host/group config properties don't work if user name as DOT in it
[ https://issues.apache.org/jira/browse/HADOOP-7050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nanda kumar resolved HADOOP-7050. - Resolution: Duplicate > proxyuser host/group config properties don't work if user name as DOT in it > --- > > Key: HADOOP-7050 > URL: https://issues.apache.org/jira/browse/HADOOP-7050 > Project: Hadoop Common > Issue Type: Bug > Components: security >Reporter: Alejandro Abdelnur >Priority: Major > > If the user contains a DOT, "foo.bar", proxy user configuration fails to be > read properly and it does not kick in. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
