[jira] [Resolved] (HADOOP-14655) Update httpcore version to 4.4.6
[ https://issues.apache.org/jira/browse/HADOOP-14655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang resolved HADOOP-14655. -- Resolution: Fixed While it's in the branch, let's leave the JIRA resolved for release notes purposes. > Update httpcore version to 4.4.6 > > > Key: HADOOP-14655 > URL: https://issues.apache.org/jira/browse/HADOOP-14655 > Project: Hadoop Common > Issue Type: Sub-task >Reporter: Ray Chiang >Assignee: Ray Chiang > Fix For: 3.0.0-beta1 > > Attachments: HADOOP-14655.001.patch > > > Update the dependency > org.apache.httpcomponents:httpcore:4.4.4 > to the latest (4.4.6). -- 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-14889) Suppress the fsnamesystem lock warning on nn startup
Ajay Kumar created HADOOP-14889:
---
Summary: Suppress the fsnamesystem lock warning on nn startup
Key: HADOOP-14889
URL: https://issues.apache.org/jira/browse/HADOOP-14889
Project: Hadoop Common
Issue Type: Improvement
Reporter: Ajay Kumar
If FsNameSystemLock is held for more than 10 seconds then we log stacktrace .
We can suppress this fsnamesystem lock warning on NameNode startup.
{code}
17/09/20 21:41:39 INFO namenode.FSNamesystem: FSNamesystem write lock held for
7159 ms via
java.lang.Thread.getStackTrace(Thread.java:1552)
org.apache.hadoop.util.StringUtils.getStackTrace(StringUtils.java:945)
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.writeUnlock(FSNamesystem.java:1659)
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:1074)
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:703)
org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:688)
org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:752)
org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:992)
org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:976)
org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1701)
org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1769)
Number of suppressed write-lock reports: 0
Longest write-lock held interval: 7159
{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
Re: Trunk fails
On Wed, Sep 20, 2017 at 5:12 AM, Steve Loughran wrote: > > > > > What we could do is have a patch submission process which says "if you are > playing with packaging, you must declare at the time of patch submission > that you have run a full mvn clean install". And a commit process which > says "if you commit a patch which changes the packaging, you need to do a > build before a test" > > This is a variant of what we expect for the hadoop-aws and hadoop-azure > clients where the submitter has to state the endpoint they ran the > integration test suite against. Committer is expected to rerun the test > suite locally before the commit too, for safety > > And we should all be trying 'mvn package -Pdist,native" regularly too, and > playing with the new scripts. We need to find the issues before anyone else > > For all this to work, of course, we need reproducible builds. I see my > mornings build is asking for "json-smart-2.3-SNAPSHOT.pom" as well as the > doxia stuff. Why is so much -SNAPSHOT stuff getting in? I don't even see a > ref for json-smart in our POMs For stability of packaging changes, we could also ask commiters to include in relevant commits a piece of commit metadata in the message that we issue from a jenkins job, i.e. give the job a patch and run full nightly QBT against tree with the patch in place. -- busbey
[jira] [Resolved] (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
]
Allen Wittenauer resolved HADOOP-14874.
---
Resolution: Invalid
I'm going to close this as invalid since deprecation warnings show up when
these commands are specifically used.
> 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-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Reopened] (HADOOP-14655) Update httpcore version to 4.4.6
[ https://issues.apache.org/jira/browse/HADOOP-14655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang reopened HADOOP-14655: - > Update httpcore version to 4.4.6 > > > Key: HADOOP-14655 > URL: https://issues.apache.org/jira/browse/HADOOP-14655 > Project: Hadoop Common > Issue Type: Sub-task >Reporter: Ray Chiang >Assignee: Ray Chiang > Fix For: 3.0.0-beta1 > > Attachments: HADOOP-14655.001.patch > > > Update the dependency > org.apache.httpcomponents:httpcore:4.4.4 > to the latest (4.4.6). -- 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
Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86
For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/528/ [Sep 19, 2017 9:45:41 AM] (kai.zheng) HDFS-12479. Some misuses of lock in DFSStripedOutputStream. Contributed [Sep 19, 2017 10:53:11 AM] (stevel) Revert "HADOOP-14771. hadoop-client does not include hadoop-yarn-client. [Sep 19, 2017 1:45:05 PM] (jlowe) Revert "MAPREDUCE-6958. Shuffle audit logger should log size of shuffle [Sep 19, 2017 2:13:17 PM] (jlowe) MAPREDUCE-6958. Shuffle audit logger should log size of shuffle [Sep 19, 2017 3:35:15 PM] (epayne) MAPREDUCE-6960. Shuffle Handler prints disk error stack traces for every [Sep 19, 2017 5:07:07 AM] (brahma) HDFS-12480. TestNameNodeMetrics#testTransactionAndCheckpointMetrics [Sep 19, 2017 5:55:45 AM] (brahma) HDFS-11799. Introduce a config to allow setting up write pipeline with [Sep 19, 2017 6:50:01 PM] (lei) HDFS-12449. TestReconstructStripedFile.testNNSendsErasureCodingTasks [Sep 19, 2017 8:44:42 PM] (wang) HDFS-12444. Reduce runtime of TestWriteReadStripedFile. Contributed by [Sep 19, 2017 8:48:23 PM] (wang) HDFS-12445. Correct spellings of choosen to chosen. Contributed by hu [Sep 19, 2017 11:42:20 PM] (wang) HDFS-12437. Fix test setup in TestLeaseRecoveryStriped. [Sep 20, 2017 1:31:15 AM] (junping_du) YARN-7186. Fix finicky TestContainerManager tests. Contributed by Arun [Sep 20, 2017 1:28:31 AM] (yufei) YARN-6499. Remove the doc about Schedulable#redistributeShare(). [Error replacing 'FILE' - Workspace is not accessible] - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
Re: Trunk fails
> On 19 Sep 2017, at 16:55, Allen Wittenauer wrote: > > >> On Sep 19, 2017, at 6:48 AM, Brahma Reddy Battula >> wrote: >> >> Can we run "mvn install" and "compile" for all the modules after applying >> the patch(we can skip shadeclients) > > We need to get over this idea that precommit is going to find all > problems every time. Committers actually do need to spend some time with a > patch. Besides, in this particular case, it was shading that actually broke… > > which really makes me want to remove -DskipShade from the pom.xmls. It’s > clearly getting abused. please dont What we could do is have a patch submission process which says "if you are playing with packaging, you must declare at the time of patch submission that you have run a full mvn clean install". And a commit process which says "if you commit a patch which changes the packaging, you need to do a build before a test" This is a variant of what we expect for the hadoop-aws and hadoop-azure clients where the submitter has to state the endpoint they ran the integration test suite against. Committer is expected to rerun the test suite locally before the commit too, for safety And we should all be trying 'mvn package -Pdist,native" regularly too, and playing with the new scripts. We need to find the issues before anyone else For all this to work, of course, we need reproducible builds. I see my mornings build is asking for "json-smart-2.3-SNAPSHOT.pom" as well as the doxia stuff. Why is so much -SNAPSHOT stuff getting in? I don't even see a ref for json-smart in our POMs
Hadoop 2.8.1 docs not available at http://hadoop.apache.org/docs/r2.8.1/
There are no webpages available in the below docs directory. All it lists is empty directories. http://hadoop.apache.org/docs/r2.8.1/ -Vinay
[jira] [Resolved] (HADOOP-14865) Mvnsite fail to execute macro defined in the document HDFSErasureCoding.md
[ https://issues.apache.org/jira/browse/HADOOP-14865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huafeng Wang resolved HADOOP-14865. --- Resolution: Cannot Reproduce > Mvnsite fail to execute macro defined in the document HDFSErasureCoding.md > -- > > Key: HADOOP-14865 > URL: https://issues.apache.org/jira/browse/HADOOP-14865 > Project: Hadoop Common > Issue Type: Bug > Components: build >Reporter: SammiChen >Assignee: Huafeng Wang > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-site-plugin:3.6:site (default-site) on project > hadoop-hdfs: Error parsing > '/testptch/hadoop/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HDFSErasureCoding.md': > line [-1] Error parsing the model: Unable to execute macro in the document: > toc -> [Help 1] -- 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
