[
https://issues.apache.org/jira/browse/BEAM-9030?focusedWorklogId=366793&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-366793
]
ASF GitHub Bot logged work on BEAM-9030:
----------------------------------------
Author: ASF GitHub Bot
Created on: 06/Jan/20 17:35
Start Date: 06/Jan/20 17:35
Worklog Time Spent: 10m
Work Description: lukecwik commented on pull request #10463: [BEAM-9030]
Bump grpc to 1.26.0
URL: https://github.com/apache/beam/pull/10463#discussion_r363393068
##########
File path: vendor/README.md
##########
@@ -0,0 +1,37 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+-->
+
+# Vendored Dependencies Release
+
+The upgrading of the vendored dependencies should be performed in two steps:
+- Firstly, we need to perform a formal release of the vendored dependency.
+ The [release process](http://s.apache.org/beam-release-vendored-artifacts)
of the vendored dependency
+ is separate from the release of Apache Beam.
+- When the release of the vendored dependency is out, we can migrate Apache
Beam to use the newly released
+ vendored dependency.
+
+# How to validate the vendored dependencies
+
+The [linkage
tool](https://lists.apache.org/thread.html/eb5d95b9a33d7e32dc9bcd0f7d48ba8711d42bd7ed03b9cf0f1103f1%40%3Cdev.beam.apache.org%3E)
+is useful for the vendored dependency upgrades. It reports the linkage errors
across multiple Apache Beam artifact ids.
+
+For example, when we upgrade the vendored gRPC to 1.26.0, we could run the
linkage tool as following:
+```
+./gradlew -Ppublishing -PjavaLinkageArtifactIds=beam-vendor-grpc-1_26_0
:checkJavaLinkage
Review comment:
You need to add `-PvendoredDependenciesOnly` to enable publishing for
`beam-vendor-grpc-1_26_0`
Also, please update the comment depending on how you want to solve how to
specify the version.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 366793)
Time Spent: 5h (was: 4h 50m)
> Bump grpc to 1.26.0
> -------------------
>
> Key: BEAM-9030
> URL: https://issues.apache.org/jira/browse/BEAM-9030
> Project: Beam
> Issue Type: Bug
> Components: java-fn-execution, runner-flink
> Reporter: sunjincheng
> Assignee: sunjincheng
> Priority: Major
> Fix For: 2.19.0
>
> Time Spent: 5h
> Remaining Estimate: 0h
>
> When submitting a Python word count job to a Flink session/standalone cluster
> repeatedly, the meta space usage of the task manager of the Flink cluster
> will continuously increase (about 40MB each time). The reason is that the
> Beam classes are loaded with the user class loader in Flink and there are
> problems with the implementation of `ProcessManager`(from Beam) and
> `ThreadPoolCache`(from netty) which may cause the user class loader could not
> be garbage collected even after the job finished which causes the meta space
> memory leak eventually. You can refer to FLINK-15338[1] for more information.
> Regarding to `ProcessManager`, I have created a JIRA BEAM-9006[2] to track
> it. Regarding to `ThreadPoolCache`, it is a Netty problem and has been fixed
> in NETTY#8955[3]. Netty 4.1.35 Final has already included this fix and GRPC
> 1.22.0 has already dependents on Netty 4.1.35 Final. So we need to bump the
> version of GRPC to 1.22.0+ (currently 1.21.0).
>
> What do you think?
> [1] https://issues.apache.org/jira/browse/FLINK-15338
> [2] https://issues.apache.org/jira/browse/BEAM-9006
> [3] [https://github.com/netty/netty/pull/8955]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
