[
https://issues.apache.org/jira/browse/IMPALA-7051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16483444#comment-16483444
]
ASF subversion and git services commented on IMPALA-7051:
---------------------------------------------------------
Commit 23e11dc72662417059b1b7337d69e78c2ac4ba65 in impala's branch
refs/heads/master from [~philip]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=23e11dc ]
IMPALA-7051: Serialize Maven invocations.
I've observed some rare cases where Impala fails to build. I believe
it's because two Maven targets (yarn-extras and ext-data-source) are
being executed simultaneously. Maven's handling of ~/.m2/repository,
for example, is known to be not safe.
This patch serializes the Maven builds with the following
dependency graph:
fe -> yarn-extras -> ext-data-source -> impala-parent
The ordering of yarn-extras -> ext-data-source is arbitrary.
I decided that this artificial dependency was the clearest
way to prevent parallel executions. Having mvn-quiet.sh
take a lock seemed considerably more complex.
Change-Id: Ie24f34f421bc7dcf9140938464d43400da95275e
Reviewed-on: http://gerrit.cloudera.org:8080/10460
Reviewed-by: Tim Armstrong <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Concurrent Maven invocations can break build
> --------------------------------------------
>
> Key: IMPALA-7051
> URL: https://issues.apache.org/jira/browse/IMPALA-7051
> Project: IMPALA
> Issue Type: Task
> Components: Infrastructure
> Reporter: Philip Zeyliger
> Assignee: Philip Zeyliger
> Priority: Major
>
> Rarely I've seen our build fail when executing two Maven targets
> simultaneously. Maven isn't really safe for concurrent execution (e.g.,
> ~/.m2/repository has no locking).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
