sk0x50 commented on a change in pull request #674:
URL: https://github.com/apache/ignite-3/pull/674#discussion_r823593390
##########
File path:
modules/runner/src/main/java/org/apache/ignite/internal/app/IgniteImpl.java
##########
@@ -332,6 +333,13 @@ public void start(@Nullable String cfg) {
// Deploy all registered watches because all components are ready
and have registered their listeners.
metaStorageMgr.deployWatches();
+ baselineMgr.listenBaselineChange(ctx -> {
+ // TODO: Multi invoke supposed to be here
https://issues.apache.org/jira/browse/IGNITE-16063
+ metaStorageMgr.put(new ByteArray("some key"), new byte[0]);
Review comment:
> I could change it, if we decide to merge it not only to the feature
branch, but to the main also
In any case, the name of a property should be meaningful. IMHO, `some key`
is not good enough for the feature branch as well.
##########
File path:
modules/baseline/src/main/java/org/apache/ignite/internal/baseline/BaselineManager.java
##########
@@ -31,32 +38,29 @@
// TODO: https://issues.apache.org/jira/browse/IGNITE-14716 Adapt concept of
baseline topology IEP-4.
@SuppressWarnings({"FieldCanBeLocal", "unused"})
public class BaselineManager implements IgniteComponent {
- /** Configuration manager in order to handle and listen baseline specific
configuration. */
- private final ConfigurationManager configurationMgr;
-
- /**
- * MetaStorage manager in order to watch private distributed baseline
specific configuration, cause ConfigurationManger handles only
- * public configuration.
- */
- private final MetaStorageManager metastorageMgr;
+ /** Cluster configuration in order to handle and listen baseline specific
configuration. */
+ private final ClusterConfiguration clusterConfiguration;
/** Cluster network service in order to retrieve information about current
cluster nodes. */
private final ClusterService clusterSvc;
+ /** Busy lock to stop synchronously. */
+ private final IgniteSpinBusyLock busyLock = new IgniteSpinBusyLock();
+
+ /** Prevents double stopping the component. */
+ AtomicBoolean stopGuard = new AtomicBoolean();
Review comment:
I dont think, that is a good idea to tune concrete implementation for
test purposes. In my understanding, this should be properly handled by test
itself. Perhaps, we need to introduce something like `IgniteComponentAdapter`
that should take care of starting/stopping a component multiple times.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
