You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Laurent Goujon (Jira)" <ji...@apache.org> on 2020/05/07 03:40:00 UTC
[jira] [Resolved] (CALCITE-3965) Excessive time waiting on
DiffRepository lock
[ https://issues.apache.org/jira/browse/CALCITE-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Laurent Goujon resolved CALCITE-3965.
-------------------------------------
Fix Version/s: 1.23.0
Resolution: Fixed
Changed merged as [0220166|https://github.com/apache/calcite/commit/022016611091fdc021686aaf1a44f5217b4b3d30]
> Excessive time waiting on DiffRepository lock
> ---------------------------------------------
>
> Key: CALCITE-3965
> URL: https://issues.apache.org/jira/browse/CALCITE-3965
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: Laurent Goujon
> Assignee: Laurent Goujon
> Priority: Major
> Fix For: 1.23.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When running the whole test suite from commandline, tests are parallelized and gradle/junit tries to use as many cores as possible (16 on my machine). But the tests take a very long time, approximatevely 90minutes on my machine, and several of them failed because they took too long to complete.
> Using jstack to look at the threads state while tests are running show that most of them are waiting on {{DiffRepository}} methods ({{DiffRepository#expand}} in most cases) while one of the thread obtained the lock (and is usually flushing data on disk).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)