You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Jonathan Eagles (JIRA)" <ji...@apache.org> on 2016/08/16 00:19:20 UTC
[jira] [Commented] (TEZ-3413) ConcurrentModificationException in
HistoryEventTimelineConversion for AppLaunchedEvent
[ https://issues.apache.org/jira/browse/TEZ-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421940#comment-15421940 ]
Jonathan Eagles commented on TEZ-3413:
--------------------------------------
After initial analysis, one culprit may be DAGClientServer#startService. It is initialized with the DAGAppMaster conf and does not make a copy in serviceInit. This would allow conf.set due to RPC.setProtocolEngine during conf.iterator() for convertConfigurationToATSMap. There could be other services like this as well.
> ConcurrentModificationException in HistoryEventTimelineConversion for AppLaunchedEvent
> --------------------------------------------------------------------------------------
>
> Key: TEZ-3413
> URL: https://issues.apache.org/jira/browse/TEZ-3413
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Jonathan Eagles
> Priority: Blocker
>
> AppLaunchedEvent contains the amConfig from the DAGAppMaster that is used to initialized several services. If Configuration#iterator is called while someone calls Configuration#set, HistoryEventTimelineConversion#convertAppLaunchedEvent will throw a CME.
> {code}
> java.util.ConcurrentModificationException
> at java.util.Hashtable$Enumerator.next(Hashtable.java:1367)
> at org.apache.hadoop.conf.Configuration.iterator(Configuration.java:2451)
> at org.apache.tez.dag.history.utils.DAGUtils.convertConfigurationToATSMap(DAGUtils.java:449)
> at org.apache.tez.dag.history.logging.ats.HistoryEventTimelineConversion.convertAppLaunchedEvent(HistoryEventTimelineConversion.java:177)
> at org.apache.tez.dag.history.logging.ats.HistoryEventTimelineConversion.convertToTimelineEntity(HistoryEventTimelineConversion.java:69)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)