eolivelli commented on a change in pull request #509: Issue 508: Introduce lifecycle components for managing components in bookie server URL: https://github.com/apache/bookkeeper/pull/509#discussion_r139549352
########## File path: bookkeeper-common/src/main/java/org/apache/bookkeeper/common/component/ComponentStarter.java ########## @@ -0,0 +1,71 @@ +/* + * 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. + */ + +package org.apache.bookkeeper.common.component; + +import java.util.concurrent.CountDownLatch; +import lombok.extern.slf4j.Slf4j; + +/** + * Utils to start components. + */ +@Slf4j +public class ComponentStarter { + + static class ComponentShutdownHook implements Runnable { + + private final LifecycleComponent component; + private final CountDownLatch aliveLatch; + + ComponentShutdownHook(LifecycleComponent component, + CountDownLatch aliveLatch) { + this.component = component; + this.aliveLatch = aliveLatch; + } + + @Override + public void run() { + aliveLatch.countDown(); + log.info("Closing component {} in shutdown hook.", component.getName()); + try { + component.close(); + log.info("Closed component {} in shutdown hook successfully. Exiting.", component.getName()); + } catch (Exception e) { + log.error("Failed to close component {} in shutdown hook gracefully, Exiting anyway", + component.getName(), e); + } + } + + } + + /** + * Start a component and register a shutdown hook. + * + * @param component component to start. + */ + public static void startComponent(LifecycleComponent component, + CountDownLatch aliveLatch) { + Runtime.getRuntime().addShutdownHook(new Thread( Review comment: Before this change the hook applies only to the bookie server. Now we are adding an hook for every component. There will be no control on when these hooks will run and in which order. We could run into deadlocks if there is no coordination of components and for their own pluggable nature we won't have this ability of coordination. Maybe this is ok for the BookieServer in order to try to do a clean shutdown of journals and storage. This usually can bring better recovery. The hook is not guaranteed to be executed, so functionally we can drop it. For tests we should disable it anyway because it induces a strong reference to the component and this is a memory leak. We don't suffer about this now because we are always forking new processes. Sorry for typos, using mobile ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on 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
