Re: Unassigned Hadoop jiras with patch available

2019-08-15 Thread Wei-Chiu Chuang
Interestingly enough,
I think I can create new wiki, but I don't see a button to edit existing
wiki.

On Thu, Aug 15, 2019 at 6:24 AM Masatake Iwasaki <
iwasak...@oss.nttdata.co.jp> wrote:

> Hi Wei-Chiu Chuang,
>
> Thanks for doing this and sorry for late reply.
>
> HowToCommit[1] wiki has description about how to do this in "Adding
> Contributors role" section but it does not explicitly say when it
> should be done.
>
> [1] https://cwiki.apache.org/confluence/display/HADOOP2/HowToCommit
>
> This could be stated as a part of "Review" process.  Also adding link
> to your JIRA filter to the wiki and encouraging housekeeping would be
> nice.
>
> # I don't have permission to edit the page..
>
> Regards,
> Masatake Iwasaki
>
> On 8/2/19 06:41, Wei-Chiu Chuang wrote:
> > I assigned all jiras with patch available that are created since 2019. If
> > you have jiras that you are actively working on that you can't assign to
> > yourself, please let me know.
> >
> > On Wed, Jul 31, 2019 at 3:11 PM Wei-Chiu Chuang 
> wrote:
> >
> >> I was told the filter is private. I am sorry.
> >>
> >> This one should be good:
> >>
> https://issues.apache.org/jira/issues/?jql=project%20in%20(HADOOP%2C%20HDFS%2CYARN%2CMAPREDUCE%2CHDDS%2CSUBMARINE)%20AND%20status%20%3D%20%22Patch%20Available%22%20AND%20assignee%20%3D%20EMPTY%20ORDER%20BY%20created%20DESC%2C%20updated%20DESC
> >>
> >> On Wed, Jul 31, 2019 at 3:02 PM Wei-Chiu Chuang 
> >> wrote:
> >>
> >>> I am using this jira filter to find jiras with patch available but
> >>> unassigned.
> >>>
> >>>
> https://issues.apache.org/jira/issues/?filter=12346814=project%20in%20(HADOOP%2C%20HDFS%2CYARN%2CMAPREDUCE%2CHDDS%2CSUBMARINE)%20AND%20status%20%3D%20%22Patch%20Available%22%20AND%20assignee%20%3D%20EMPTY%20ORDER%20BY%20created%20DESC%2C%20updated%20DESC
> >>>
> >>> In most cases, these jiras are unassigned because the contributor who
> >>> posted the patch are the first-timers and do not have the contributor
> role
> >>> in the jira. It's very common for those folks to get overlooked.
> >>>
> >>> Hadoop PMCs, if you have the JIRA administrator permission, please help
> >>> grant contributor access to these contributors. You help keep the
> project
> >>> more friendly to new-comers.
> >>>
> >>> You can do so by going to JIRA --> (upper right, click on the gear next
> >>> to your profile avatar) --> Projects --> click on the project (say
> Hadoop
> >>> HDFS) --> Roles --> View Project Roles --> Add users to a role --> add
> to
> >>> Contributor list, or if the Contributor list is full, add to
> Contributor1
> >>> list.
> >>>
> >>> Or you can go to
> >>>
> https://issues.apache.org/jira/plugins/servlet/project-config/HDFS/roles
> to
> >>> add the contributor access for HDFS. Similarly goes for Hadoop Common
> and
> >>> other sub-projects.
> >>>
>
>


Re: [DISCUSS] Hadoop 2019 Release Planning

2019-08-15 Thread Masatake Iwasaki

Hi Wangda,

Thanks for bringing this up.

> I think it is the time to do maintenance releases of 3.1/3.2 and do a 
minor

> release for 3.3.0.

3.3.0 seems to have some blocker issues.

  project in ("Hadoop Common", "Hadoop HDFS", "Hadoop Map/Reduce", 
"Hadoop YARN") AND "Target Version/s" = 3.3.0 AND priority = Blocker AND 
status != Resolved


I'm reviewing HADOOP-15958 now.


On 8/13/19 02:33, Jonathan Hung wrote:

Hi Wangda, Thanks for starting the discussion. We would also like to
release 2.10.0 which was discussed previously
 and
at various contributor meetups. I'm interested in being release manager for
that.

Thanks,

Jonathan Hung


On Fri, Aug 9, 2019 at 7:59 PM Wangda Tan  wrote:


Hi all,

Hope this email finds you well

I want to hear your thoughts about what should be the release plan for
2019.

In 2018, we released:
- 1 maintenance release of 2.6
- 3 maintenance releases of 2.7
- 3 maintenance releases of 2.8
- 3 releases of 2.9
- 4 releases of 3.0
- 2 releases of 3.1

Total 16 releases in 2018.

In 2019, by far we only have two releases:
- 1 maintenance release of 3.1
- 1 minor release of 3.2.

However, the community put a lot of efforts to stabilize features of
various release branches.
There're:
- 217 fixed patches in 3.1.3 [1]
- 388 fixed patches in 3.2.1 [2]
- 1172 fixed patches in 3.3.0 [3] (OMG!)

I think it is the time to do maintenance releases of 3.1/3.2 and do a minor
release for 3.3.0.

In addition, I saw community discussion to do a 2.8.6 release for security
fixes.

Any other releases? I think there're release plans for Ozone as well. And
please add your thoughts.

Volunteers welcome! If you have interests to run a release as Release
Manager (or co-Resource Manager), please respond to this email thread so we
can coordinate.

Thanks,
Wangda Tan

[1] project in (YARN, HADOOP, MAPREDUCE, HDFS) AND resolution = Fixed AND
fixVersion = 3.1.3
[2] project in (YARN, HADOOP, MAPREDUCE, HDFS) AND resolution = Fixed AND
fixVersion = 3.2.1
[3] project in (YARN, HADOOP, MAPREDUCE, HDFS) AND resolution = Fixed AND
fixVersion = 3.3.0




-
To unsubscribe, e-mail: mapreduce-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-h...@hadoop.apache.org



Re: Unassigned Hadoop jiras with patch available

2019-08-15 Thread Masatake Iwasaki

Hi Wei-Chiu Chuang,

Thanks for doing this and sorry for late reply.

HowToCommit[1] wiki has description about how to do this in "Adding
Contributors role" section but it does not explicitly say when it
should be done.

[1] https://cwiki.apache.org/confluence/display/HADOOP2/HowToCommit

This could be stated as a part of "Review" process.  Also adding link
to your JIRA filter to the wiki and encouraging housekeeping would be
nice.

# I don't have permission to edit the page..

Regards,
Masatake Iwasaki

On 8/2/19 06:41, Wei-Chiu Chuang wrote:

I assigned all jiras with patch available that are created since 2019. If
you have jiras that you are actively working on that you can't assign to
yourself, please let me know.

On Wed, Jul 31, 2019 at 3:11 PM Wei-Chiu Chuang  wrote:


I was told the filter is private. I am sorry.

This one should be good:
https://issues.apache.org/jira/issues/?jql=project%20in%20(HADOOP%2C%20HDFS%2CYARN%2CMAPREDUCE%2CHDDS%2CSUBMARINE)%20AND%20status%20%3D%20%22Patch%20Available%22%20AND%20assignee%20%3D%20EMPTY%20ORDER%20BY%20created%20DESC%2C%20updated%20DESC

On Wed, Jul 31, 2019 at 3:02 PM Wei-Chiu Chuang 
wrote:


I am using this jira filter to find jiras with patch available but
unassigned.

https://issues.apache.org/jira/issues/?filter=12346814=project%20in%20(HADOOP%2C%20HDFS%2CYARN%2CMAPREDUCE%2CHDDS%2CSUBMARINE)%20AND%20status%20%3D%20%22Patch%20Available%22%20AND%20assignee%20%3D%20EMPTY%20ORDER%20BY%20created%20DESC%2C%20updated%20DESC

In most cases, these jiras are unassigned because the contributor who
posted the patch are the first-timers and do not have the contributor role
in the jira. It's very common for those folks to get overlooked.

Hadoop PMCs, if you have the JIRA administrator permission, please help
grant contributor access to these contributors. You help keep the project
more friendly to new-comers.

You can do so by going to JIRA --> (upper right, click on the gear next
to your profile avatar) --> Projects --> click on the project (say Hadoop
HDFS) --> Roles --> View Project Roles --> Add users to a role --> add to
Contributor list, or if the Contributor list is full, add to Contributor1
list.

Or you can go to
https://issues.apache.org/jira/plugins/servlet/project-config/HDFS/roles to
add the contributor access for HDFS. Similarly goes for Hadoop Common and
other sub-projects.




-
To unsubscribe, e-mail: mapreduce-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-h...@hadoop.apache.org



Apache Hadoop qbt Report: branch2+JDK7 on Linux/x86

2019-08-15 Thread Apache Jenkins Server
For more details, see 
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/414/

[Aug 14, 2019 3:35:14 AM] (iwasakims) HDFS-14423. Percent (%) and plus (+) 
characters no longer work in


[Error replacing 'FILE' - Workspace is not accessible]

-
To unsubscribe, e-mail: mapreduce-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-h...@hadoop.apache.org

Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

2019-08-15 Thread Apache Jenkins Server
For more details, see 
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/1229/

[Aug 14, 2019 3:24:03 AM] (github) HADOOP-16495. Fix invalid metric types in 
PrometheusMetricsSink (#1244)
[Aug 14, 2019 3:27:37 AM] (aengineer) HDDS-1920. Place ozone.om.address config 
key default value in
[Aug 14, 2019 3:34:06 AM] (aengineer) HDDS-1956. Aged IO Thread exits on first 
read
[Aug 14, 2019 5:02:54 AM] (aengineer) HDDS-1915. Remove hadoop script from 
ozone distribution
[Aug 14, 2019 5:04:31 AM] (aengineer) HDDS-1832 : Improve logging for 
PipelineActions handling in SCM and
[Aug 14, 2019 6:07:02 AM] (aengineer) HDDS-1947. fix naming issue for 
ScmBlockLocationTestingClient.
[Aug 14, 2019 6:12:44 AM] (aengineer) HDDS-1929. OM started on recon host in 
ozonesecure compose
[Aug 14, 2019 6:26:47 AM] (aengineer) HDDS-1914. Ozonescript example 
docker-compose cluster can't be started
[Aug 14, 2019 8:16:23 AM] (bibinchundatt) YARN-9747. Reduce additional namenode 
call by
[Aug 14, 2019 8:50:26 AM] (gabor.bota) HADOOP-16500 S3ADelegationTokens to only 
log at debug on startup
[Aug 14, 2019 1:09:45 PM] (nanda) HDDS-1965. Compile error due to leftover 
ScmBlockLocationTestIngClient
[Aug 14, 2019 2:30:35 PM] (weichiu) HDFS-14595. HDFS-11848 breaks API 
compatibility. Contributed by Siyao
[Aug 14, 2019 2:58:22 PM] (snemeth) YARN-9140. Code cleanup in 
ResourcePluginManager.initialize and in
[Aug 14, 2019 3:07:15 PM] (nanda) HDDS-1955. 
TestBlockOutputStreamWithFailures#test2DatanodesFailure
[Aug 14, 2019 3:13:54 PM] (snemeth) YARN-9133. Make tests more easy to 
comprehend in TestGpuResourceHandler.
[Aug 14, 2019 3:14:31 PM] (ayushsaxena) HDFS-14713. RBF: RouterAdmin supports 
refreshRouterArgs command but not
[Aug 14, 2019 3:35:16 PM] (954799+szilard-nemeth) YARN-9676. Add DEBUG and 
TRACE level messages to AppLogAggregatorImpl…
[Aug 14, 2019 4:34:11 PM] (aengineer) HDDS-1966. Wrong expected key ACL in 
acceptance test
[Aug 14, 2019 4:53:31 PM] (aengineer) HDDS-1964. TestOzoneClientProducer fails 
with ConnectException
[Aug 14, 2019 5:07:22 PM] (ayushsaxena) SUBMARINE-107. Reduce the scope of 
mockito-core in submarine to test.
[Aug 14, 2019 5:42:29 PM] (weichiu) YARN-9683. Remove reapDockerContainerNoPid 
left behind by YARN-9074




-1 overall


The following subsystems voted -1:
asflicense findbugs hadolint pathlen unit xml


The following subsystems voted -1 but
were configured to be filtered/ignored:
cc checkstyle javac javadoc pylint shellcheck shelldocs whitespace


The following subsystems are considered long running:
(runtime bigger than 1h  0m  0s)
unit


Specific tests:

XML :

   Parsing Error(s): 
   
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/resources/nvidia-smi-output-excerpt.xml
 
   
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/resources/nvidia-smi-output-missing-tags.xml
 
   
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/resources/nvidia-smi-output-missing-tags2.xml
 
   
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/resources/nvidia-smi-sample-output.xml
 

FindBugs :

   
module:hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-mawo/hadoop-yarn-applications-mawo-core
 
   Class org.apache.hadoop.applications.mawo.server.common.TaskStatus 
implements Cloneable but does not define or use clone method At 
TaskStatus.java:does not define or use clone method At TaskStatus.java:[lines 
39-346] 
   Equals method for 
org.apache.hadoop.applications.mawo.server.worker.WorkerId assumes the argument 
is of type WorkerId At WorkerId.java:the argument is of type WorkerId At 
WorkerId.java:[line 114] 
   
org.apache.hadoop.applications.mawo.server.worker.WorkerId.equals(Object) does 
not check for null argument At WorkerId.java:null argument At 
WorkerId.java:[lines 114-115] 

Failed junit tests :

   hadoop.hdfs.server.federation.router.TestRouterWithSecureStartup 
   hadoop.hdfs.server.federation.security.TestRouterHttpDelegationToken 
   
hadoop.yarn.server.nodemanager.containermanager.logaggregation.TestAppLogAggregatorImpl
 
   hadoop.mapreduce.v2.hs.webapp.TestHSWebApp 
   hadoop.tools.dynamometer.TestDynamometerInfra 
   hadoop.tools.dynamometer.TestDynamometerInfra 
  

   cc:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/1229/artifact/out/diff-compile-cc-root.txt
  [4.0K]

   javac:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/1229/artifact/out/diff-compile-javac-root.txt
  [332K]

   checkstyle:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/1229/artifact/out/diff-checkstyle-root.txt
  [17M]

   hadolint:

   
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/1229/artifact/out/diff-patch-hadolint.txt