You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Mashenkov (Jira)" <ji...@apache.org> on 2023/08/31 10:28:00 UTC
[jira] [Created] (IGNITE-20320) Avoid sharing HybridClock between nodes in tests
Andrey Mashenkov created IGNITE-20320:
-----------------------------------------
Summary: Avoid sharing HybridClock between nodes in tests
Key: IGNITE-20320
URL: https://issues.apache.org/jira/browse/IGNITE-20320
Project: Ignite
Issue Type: Test
Reporter: Andrey Mashenkov
As for now,
1. There are tests, where a HybridClock instance is shared among cluster nodes. This looks like a bug. Let's avoid clock sharing among nodes, or, otherwise, add a comprehensive comment, why HybridClock instance is reused.
Example: ActiveActorTest, MultiActiveActorTest, PlacementDriverManagerTest...
2. In some tests, different HybridClock instance are passed to different components.
However, there may be no nodes, but it is assumed the components belong to the same one though. This also looks like a bug.
Exampple: ItRebalanceDistributedTest...
Let's revisit all the tests, where HybridClock is created and fix these issues.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)