[jira] [Commented] (HADOOP-14836) multiple versions of maven-clean-plugin in use
[ https://issues.apache.org/jira/browse/HADOOP-14836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178451#comment-16178451 ] Huafeng Wang commented on HADOOP-14836: --- Hi [~aw], can you help to review this patch? Thanks. > multiple versions of maven-clean-plugin in use > -- > > Key: HADOOP-14836 > URL: https://issues.apache.org/jira/browse/HADOOP-14836 > Project: Hadoop Common > Issue Type: Bug > Components: build >Affects Versions: 3.0.0-beta1 >Reporter: Allen Wittenauer >Assignee: Huafeng Wang > Attachments: HADOOP-14836.001.patch > > > hadoop-yarn-ui re-declares maven-clean-plugin with 3.0 while the rest of the > source tree uses 2.5. This should get synced up. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-14713) Audit for durations that should be measured via Time.monotonicNow
[ https://issues.apache.org/jira/browse/HADOOP-14713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178321#comment-16178321 ] Chetna Chaudhari commented on HADOOP-14713: --- Thanks [~templedf] will create JIRA per package for the test classes. > Audit for durations that should be measured via Time.monotonicNow > - > > Key: HADOOP-14713 > URL: https://issues.apache.org/jira/browse/HADOOP-14713 > Project: Hadoop Common > Issue Type: Improvement >Reporter: Jason Lowe >Assignee: Chetna Chaudhari > Labels: newbie > > Whenever we are measuring a time delta or duration in the same process, the > timestamps probably should be using Time.monotonicNow rather than Time.now or > System.currentTimeMillis. The latter two are directly reading the system > clock which can move faster or slower than actual time if the system is > undergoing a time adjustment (e.g.: adjtime or admin sets a new system time). > We should go through the code base and identify places where the code is > using the system clock but really should be using monotonic time. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-14220) Enhance S3GuardTool with bucket-info and set-capacity commands, tests
[ https://issues.apache.org/jira/browse/HADOOP-14220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178278#comment-16178278 ] Steve Loughran commented on HADOOP-14220: - I'd done my changes out of sync with yours, so no, not intentional. Let me cut it again > Enhance S3GuardTool with bucket-info and set-capacity commands, tests > - > > Key: HADOOP-14220 > URL: https://issues.apache.org/jira/browse/HADOOP-14220 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 >Affects Versions: 3.0.0-beta1 >Reporter: Steve Loughran >Assignee: Steve Loughran > Attachments: HADOOP-14220-006.patch, HADOOP-14220-008.patch, > HADOOP-14220-009.patch, HADOOP-14220-010.patch, HADOOP-14220-012.patch, > HADOOP-14220-013.patch, HADOOP-14220-013.patch, HADOOP-14220-014.patch, > HADOOP-14220-HADOOP-13345-001.patch, HADOOP-14220-HADOOP-13345-002.patch, > HADOOP-14220-HADOOP-13345-003.patch, HADOOP-14220-HADOOP-13345-004.patch, > HADOOP-14220-HADOOP-13345-005.patch > > > Add a diagnostics command to s3guard which does whatever we need to diagnose > problems for a specific (named) s3a url. This is something which can be > attached to bug reports as well as used by developers. > * Properties to log (with provenance attribute, which can track bucket > overrides: s3guard metastore setup, autocreate, capacity, > * table present/absent > * # of keys in DDB table for that bucket? > * any other stats? -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-14874) Secure NFS and DataNode related environment variable need to be added as hadoop_deprecate_envvar in hdfs_config.sh
[
https://issues.apache.org/jira/browse/HADOOP-14874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178172#comment-16178172
]
Mukul Kumar Singh commented on HADOOP-14874:
My bad, please ignore my last comment.
> Secure NFS and DataNode related environment variable need to be added as
> hadoop_deprecate_envvar in hdfs_config.sh
> --
>
> Key: HADOOP-14874
> URL: https://issues.apache.org/jira/browse/HADOOP-14874
> Project: Hadoop Common
> Issue Type: Bug
> Components: scripts
>Reporter: Mukul Kumar Singh
>Assignee: Mukul Kumar Singh
> Attachments: HADOOP-14874.001.patch
>
>
> Following config variables should be added as hadoop_deprecate_envvar in
> hdfs_config.sh
> {code}
> HADOOP_PRIVILEGED_NFS_USER
> HADOOP_SECURE_DN_PID_DIR
> HADOOP_PRIVILEGED_NFS_PID_DIR
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-14874) Secure NFS and DataNode related environment variable need to be added as hadoop_deprecate_envvar in hdfs_config.sh
[
https://issues.apache.org/jira/browse/HADOOP-14874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mukul Kumar Singh updated HADOOP-14874:
---
Attachment: HADOOP-14874.001.patch
> Secure NFS and DataNode related environment variable need to be added as
> hadoop_deprecate_envvar in hdfs_config.sh
> --
>
> Key: HADOOP-14874
> URL: https://issues.apache.org/jira/browse/HADOOP-14874
> Project: Hadoop Common
> Issue Type: Bug
> Components: scripts
>Reporter: Mukul Kumar Singh
>Assignee: Mukul Kumar Singh
> Attachments: HADOOP-14874.001.patch
>
>
> Following config variables should be added as hadoop_deprecate_envvar in
> hdfs_config.sh
> {code}
> HADOOP_PRIVILEGED_NFS_USER
> HADOOP_SECURE_DN_PID_DIR
> HADOOP_PRIVILEGED_NFS_PID_DIR
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-14874) Secure NFS and DataNode related environment variable need to be added as hadoop_deprecate_envvar in hdfs_config.sh
[
https://issues.apache.org/jira/browse/HADOOP-14874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178132#comment-16178132
]
Mukul Kumar Singh commented on HADOOP-14874:
Hi [~aw], I feel we should still add deprecation for
{{HADOOP_SECURE_DN_PID_DIR}}, {{HADOOP_PRIVILEGED_NFS_PID_DIR}},
{{HADOOP_SECURE_DN_LOG_DIR}} and {{HADOOP_PRIVILEGED_NFS_LOG_DIR}}. These
aren't still marked as deprecated in hdfs-config.sh
I was thinking of adding the following lines of code in hdfs-config.sh
{code}
hadoop_deprecate_envvar HADOOP_SECURE_DN_PID_DIR HADOOP_SECURE_PID_DIR
hadoop_deprecate_envvar HADOOP_PRIVILEGED_NFS_PID_DIR HADOOP_SECURE_PID_DIR
hadoop_deprecate_envvar HADOOP_SECURE_DN_LOG_DIR HADOOP_SECURE_LOG_DIR
hadoop_deprecate_envvar HADOOP_PRIVILEGED_NFS_LOG_DIR HADOOP_SECURE_LOG_DIR
{code}
> Secure NFS and DataNode related environment variable need to be added as
> hadoop_deprecate_envvar in hdfs_config.sh
> --
>
> Key: HADOOP-14874
> URL: https://issues.apache.org/jira/browse/HADOOP-14874
> Project: Hadoop Common
> Issue Type: Bug
> Components: scripts
>Reporter: Mukul Kumar Singh
>Assignee: Mukul Kumar Singh
>
> Following config variables should be added as hadoop_deprecate_envvar in
> hdfs_config.sh
> {code}
> HADOOP_PRIVILEGED_NFS_USER
> HADOOP_SECURE_DN_PID_DIR
> HADOOP_PRIVILEGED_NFS_PID_DIR
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
