belliottsmith commented on code in PR #38:
URL: https://github.com/apache/cassandra-accord/pull/38#discussion_r1177117401


##########
accord-core/src/main/java/accord/local/CommandStores.java:
##########
@@ -65,19 +67,23 @@ CommandStores<?> create(NodeTimeService time,
         private final DataStore store;
         private final ProgressLog.Factory progressLogFactory;
         private final CommandStore.Factory shardFactory;
+        private final RandomSource random;
 
-        Supplier(NodeTimeService time, Agent agent, DataStore store, 
ProgressLog.Factory progressLogFactory, CommandStore.Factory shardFactory)
+        Supplier(NodeTimeService time, Agent agent, DataStore store, 
RandomSource random, ProgressLog.Factory progressLogFactory, 
CommandStore.Factory shardFactory)
         {
             this.time = time;
             this.agent = agent;
             this.store = store;
+            this.random = random;
             this.progressLogFactory = progressLogFactory;
             this.shardFactory = shardFactory;
         }
 
         CommandStore create(int id, RangesForEpochHolder rangesForEpoch)
         {
-            return shardFactory.create(id, time, agent, store, 
progressLogFactory, rangesForEpoch);
+            CommandStore store = shardFactory.create(id, time, agent, 
this.store, progressLogFactory, rangesForEpoch);
+            store.execute(() -> CommandStore.register(store));

Review Comment:
   I mean that the `SingleThread` (and extensions) do not need to register, or 
use the `Unsafe` implementation at all, since their implementation of 
`inStore()` is:
   
   ```
           @Override
           public boolean inStore()
           {
               return thread == Thread.currentThread();
           }
   ```
   
   However, the other `Synchronised` and `DelayedCommandStore` do need some 
help, and they rely on `Unsafe` to implement `inStore`... except that their 
`register` call on construction won't work in tandem with these calls.



-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to