You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by GitBox <gi...@apache.org> on 2020/06/01 23:12:27 UTC

[GitHub] [samza] kw2542 commented on a change in pull request #1370: SAMZA-2537: Fix JobCoordinatorLaunchUtil's execution sequence.

kw2542 commented on a change in pull request #1370:
URL: https://github.com/apache/samza/pull/1370#discussion_r433536628



##########
File path: samza-core/src/main/java/org/apache/samza/clustermanager/JobCoordinatorLaunchUtil.java
##########
@@ -59,6 +59,8 @@ public static void run(SamzaApplication app, Config config) {
     }
 
     Config fullConfig = jobConfigs.get(0);
+    // Create coordinator stream if does not exist before fetching launch config from it.
+    CoordinatorStreamUtil.createCoordinatorStream(fullConfig);

Review comment:
       Yes, we are actually running createCoordinateStream() every time in writeConfigToCoordinatorStream().




----------------------------------------------------------------
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:
users@infra.apache.org