narendly commented on a change in pull request #787: Fix tests in
apache/zooscalability and rebase from apache/master
URL: https://github.com/apache/helix/pull/787#discussion_r382278094
##########
File path: helix-core/src/main/java/org/apache/helix/task/TaskUtil.java
##########
@@ -1043,23 +1043,40 @@ public static void purgeExpiredJobs(String workflow,
WorkflowConfig workflowConf
* @param dataProvider
* @param manager
*/
- public static void workflowGarbageCollection(WorkflowControllerDataProvider
dataProvider,
+ public static void workflowGarbageCollection(final
WorkflowControllerDataProvider dataProvider,
final HelixManager manager) {
// Garbage collections for conditions where workflow context exists but
config is missing.
- Map<String, ZNRecord> contexts = dataProvider.getContexts();
- HelixDataAccessor accessor = manager.getHelixDataAccessor();
- HelixPropertyStore<ZNRecord> propertyStore =
manager.getHelixPropertyStore();
+ Set<String> existingContexts;
+ /*
+ * Here try-catch is used to avoid concurrent modification exception while
doing deep copy.
+ * Map.keySet() can produce concurrent modification exception.
+ * Reason: If the map is modified while an iteration over the set is in
progress, concurrent
+ * modification exception will be thrown.
+ */
+ try {
+ existingContexts = new HashSet<>(dataProvider.getContexts().keySet());
+ } catch (Exception e) {
Review comment:
Please create a separate issue tracking that item. In my opinion, catching
ConcurrentModificationException is awkward and I personally prefer catching a
general Exception.
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
