-
Notifications
You must be signed in to change notification settings - Fork 135
IGNITE-15298 Partitions raft snapshots #285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
fe17e44 to
d91b3d8
Compare
modules/storage-api/src/main/java/org/apache/ignite/internal/storage/Storage.java
Outdated
Show resolved
Hide resolved
...storage-rocksdb/src/main/java/org/apache/ignite/internal/storage/rocksdb/RocksDbStorage.java
Outdated
Show resolved
Hide resolved
...storage-rocksdb/src/main/java/org/apache/ignite/internal/storage/rocksdb/RocksDbStorage.java
Outdated
Show resolved
Hide resolved
...tegrationTest/java/org/apache/ignite/raft/client/service/ITAbstractListenerSnapshotTest.java
Outdated
Show resolved
Hide resolved
...tegrationTest/java/org/apache/ignite/raft/client/service/ITAbstractListenerSnapshotTest.java
Outdated
Show resolved
Hide resolved
...tegrationTest/java/org/apache/ignite/raft/client/service/ITAbstractListenerSnapshotTest.java
Outdated
Show resolved
Hide resolved
...tegrationTest/java/org/apache/ignite/raft/client/service/ITAbstractListenerSnapshotTest.java
Outdated
Show resolved
Hide resolved
| * @param interactedAfterSnapshot {@code true} whether raft group was interacted with after the snapshot operation. | ||
| * @return Closure. | ||
| */ | ||
| public abstract BooleanSupplier snapshotCheckClosure(JRaftServerImpl restarted, boolean interactedAfterSnapshot); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually I think that all these abstract methods are a sign of over-engineering. Do we really need an abstract class for these two tests? I think it is easier to copy-paste the test itself....
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tests are basically the same, any change in the raft group API would require changes in two places
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but all these abstract methods show that they are not really the same, only the overall test scenario
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think raft set up, stop and restart operations are too complicated to copy-paste them. I don't see how abstract tests can hurt us
...les/table/src/integrationTest/java/org/apache/ignite/distributed/ITTablePersistenceTest.java
Outdated
Show resolved
Hide resolved
...les/table/src/integrationTest/java/org/apache/ignite/distributed/ITTablePersistenceTest.java
Outdated
Show resolved
Hide resolved
e1265df to
ba67f54
Compare
modules/rocksdb-common/src/main/java/org/apache/ignite/internal/rocksdb/RocksUtils.java
Outdated
Show resolved
Hide resolved
modules/rocksdb-common/src/main/java/org/apache/ignite/internal/rocksdb/RocksUtils.java
Outdated
Show resolved
Hide resolved
d17bd70 to
92362fe
Compare
Co-authored-by: Alexander Polovtcev <alex.polovtcev@gmail.com>
92362fe to
2d4f121
Compare
https://issues.apache.org/jira/browse/IGNITE-15298