nizhikov commented on a change in pull request #8911:
URL: https://github.com/apache/ignite/pull/8911#discussion_r601275172
##########
File path:
modules/core/src/test/java/org/apache/ignite/internal/metric/SystemViewSelfTest.java
##########
@@ -909,6 +945,648 @@ private void checkScanQueryView(IgniteEx client1,
IgniteEx client2, SystemView<S
assertTrue(found1 && found2);
}
+
+ /** */
+ @Test
+ public void testAtomicSequence() throws Exception {
+ try (IgniteEx g0 = startGrid(0);
+ IgniteEx g1 = startGrid(1)) {
+ IgniteAtomicSequence s1 = g0.atomicSequence("seq-1", 42, true);
+ IgniteAtomicSequence s2 = g0.atomicSequence("seq-2",
+ new
AtomicConfiguration().setBackups(1).setGroupName("my-group"), 43, true);
+
+ s1.batchSize(42);
+
+ SystemView<AtomicSequenceView> seqs0 =
g0.context().systemView().view(SEQUENCES_VIEW);
+ SystemView<AtomicSequenceView> seqs1 =
g1.context().systemView().view(SEQUENCES_VIEW);
+
+ assertEquals(2, seqs0.size());
+ assertEquals(0, seqs1.size());
Review comment:
> also by a reason that the backup value is 1 and the ds should already
exist on g1
Ignite Data structures has 2 place that reflects their state:
1. system cache
2. `DataStructureProcessor#dsMap` (`CacheDataStructuresManager`)
I prefer to show second place, because, scanning a cache may involve network
operations.
And network operations violate the local nature of the system views.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
