tweise commented on a change in pull request #11084: [BEAM-9474] Improve 
robustness of BundleFactory and ProcessEnvironment
URL: https://github.com/apache/beam/pull/11084#discussion_r389984708
 
 

 ##########
 File path: 
runners/java-fn-execution/src/main/java/org/apache/beam/runners/fnexecution/control/DefaultJobBundleFactory.java
 ##########
 @@ -166,11 +168,20 @@ public static DefaultJobBundleFactory create(
         CacheBuilder.newBuilder()
             .removalListener(
                 (RemovalNotification<Environment, WrappedSdkHarnessClient> 
notification) -> {
-                  int refCount = notification.getValue().unref();
-                  LOG.debug(
-                      "Removed environment {} with {} remaining bundle 
references.",
-                      notification.getKey(),
-                      refCount);
+                  WrappedSdkHarnessClient client = notification.getValue();
+                  int refCount = client.unref();
+                  // Double-check to trigger closing of all environments in 
case the "refing" does
+                  // not clean them up during operator shutdown. This is 
necessary in some
+                  // situations, e.g when the bundle cannot be closed and thus 
the ref cannot be
+                  // released. All environment types ensure they can only be 
closed once.
+                  if (refCount > 0) {
+                    LOG.warn(
+                        "Clearing remaining {} bundle references from 
environment {} to ensure it shuts down.",
+                        refCount,
+                        notification.getKey());
+                    //noinspection StatementWithEmptyBody
 
 Review comment:
   Why is this needed (with the log statement above)? 

----------------------------------------------------------------
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]


With regards,
Apache Git Services

Reply via email to