Anton, Maxim, thanks for following up! Looks like a good enough trade-off.
Sorry, couldn't catch the conversation because of the different time zone ;)
On Tuesday, September 4, 2018, 7:54:05 p.m. GMT+9, Anton Vinogradov
wrote:
Maxim,
Let's create a branch with 10 checks of Sync and 10
Maxim,
Let's create a branch with 10 checks of Sync and 10 checks of Async.
Then, run it 20 times at TC.
This should be enough I think.
вт, 4 сент. 2018 г. в 13:09, Maxim Muzafarov :
> Anton,
>
> I agree with you 20 time is not enough. I've checked the single run of the
> test class - it consume
Anton,
I agree with you 20 time is not enough. I've checked the single run of the
test class - it consumes ~7min per each execution.
CacheSuite8 total execution timeout - 210 min, so we can perform only 30
class execution in this suite. Our strategy here is
to `20 times within single` and put into
Maxim,
20 is not 1k :)
Also, you forgot to check GridCacheRebalancingAsyncSelfTest
I'm not sure we should have exactly 1k runs, but 20 is definitely not
enough.
Roman,
I propose to use IDEA "run until failure" feature and perform test locally
(at your PC) while you're not using PC.
вт, 4 сент. 2
Roman, Anton,
I've already created additional PR [2] all and run it on TC [1].
Please, follow up with the results.
[1]
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Cache8&tab=buildTypeStatusDiv&branch_IgniteTests24Java8=pull%2F4676%2Fhead
[2] https://github.com/apache
Anton,
Thank you. I would like to recheck it. How can this (1_000 runs) be done in TC?
On Tuesday, September 4, 2018, 5:42:01 p.m. GMT+9, Anton Vinogradov
wrote:
Roman,
I see you uncommented this line.
I do not remember deadlock detail, but I remember it was the extremely rare
case.
I
Roman,
I see you uncommented this line.
I do not remember deadlock detail, but I remember it was the extremely rare
case.
I found and "fixed" it some days before merge when I had 24x7 sanity check
week :)
So, I propose to have at least 1_000 runs of this tests before keeping this
uncommented.
Roman,
I worked recently on rebalance improvements and haven't found any problems
with delayed cache rebalacne.
Agree with you - let's uncomment this and remove scary comment. Will you
create a ticket for it?
In case of any problems we can easily detec deadlock with newly configured
`FailureHandl
Hi Maxim,
I have some issues with a cluster with rebalance delay enabled, but need to
check more -- if I find it's related I'll share.Just wanted to make sure it's
not an issue anymore from someone working on rebalancing. We should remove that
comment then, it looks scary :)
--
Roman Shtykh
Hello Roman,
Did you faced with real issue of delayed rebalance or it's just only for
your personal interest?
If yes, please, share details and we will try to help you.
As for this comment I don't think he is actual. That change was in 2015.
Much has changed
within rebalance process since that ti
10 matches
Mail list logo
