KAFKA-12368: Added inmemory implementations for RemoteStorageManager and RemoteLogMetadataManager.#10218
Conversation
df6b7b3 to
2f0c2f1
Compare
74f273b to
a03cb96
Compare
b61336f to
0ce29f8
Compare
There was a problem hiding this comment.
Hmm, do we need to explicitly check if endPosition < segment.length?
There was a problem hiding this comment.
It takes Math.min(endPosition, segment.length). So, no need to have that check.
|
@kowshik I discussed the proposed changes in the call on 23rd, and I mentioned that PR is not updated with those changes. I will let you know once those changes are pushed into this PR. |
dfa913c to
96d05f9
Compare
0711931 to
3f88549
Compare
There was a problem hiding this comment.
It's kind of weird that the segment with epoch 0 is already deleted and yet we still expect the highest offset for epoch 0 to be returned.
There was a problem hiding this comment.
highestLogOffset can contain the deleted segments. highestLogOffset means the highest offset up to which the segments have been copied. Pl take a look at the comment.
…and RemoteLogMetadataManager. Added inmemory implementation for RemoteStorageManager and RemoteLogMetadataManager. A major part of inmemory RLMM will be used in the default RLMM implementation which will be based on topic storage. These will be used in unit tests for tiered storage. Added a few tests for both the implementations. This is part of tiered storage implementation, KIP-405.
Updated java doc comments and addressed typos.
Refactoring for better modularization. Addressed review comments.
| * The below table summarizes whether the segment with the respective state are available for the given methods. | ||
| * <pre> | ||
| * +---------------------------------+----------------------+------------------------+-------------------------+-------------------------+ | ||
| * | Method / SegmentState | COPY_SEGMENT_STARTED | COPY_SEGMENT_FINISHED | DELETE_SEGMENT_STARTED | DELETE_SEGMENT_STARTED | |
There was a problem hiding this comment.
typo: The title of the last column should be DELETE_SEGMENT_FINISHED.
There was a problem hiding this comment.
thanks, addressed it in the latest commit.
…and RemoteLogMetadataManager. (apache#10218) KAFKA-12368: Added inmemory implementations for RemoteStorageManager and RemoteLogMetadataManager. Added inmemory implementation for RemoteStorageManager and RemoteLogMetadataManager. A major part of inmemory RLMM will be used in the default RLMM implementation which will be based on topic storage. These will be used in unit tests for tiered storage. Added tests for both the implementations and their supported classes. This is part of tiered storage implementation, KIP-405. Reivewers: Kowshik Prakasam <kprakasam@confluent.io>, Jun Rao <junrao@gmail.com>
…and RemoteLogMetadataManager. (apache#10218) KAFKA-12368: Added inmemory implementations for RemoteStorageManager and RemoteLogMetadataManager. Added inmemory implementation for RemoteStorageManager and RemoteLogMetadataManager. A major part of inmemory RLMM will be used in the default RLMM implementation which will be based on topic storage. These will be used in unit tests for tiered storage. Added tests for both the implementations and their supported classes. This is part of tiered storage implementation, KIP-405. Reivewers: Kowshik Prakasam <kprakasam@confluent.io>, Jun Rao <junrao@gmail.com>
…and RemoteLogMetadataManager. (apache#10218) Summary: KAFKA-12368: Added inmemory implementations for RemoteStorageManager and RemoteLogMetadataManager. Added inmemory implementation for RemoteStorageManager and RemoteLogMetadataManager. A major part of inmemory RLMM will be used in the default RLMM implementation which will be based on topic storage. These will be used in unit tests for tiered storage. Added tests for both the implementations and their supported classes. This is part of tiered storage implementation, KIP-405. apache-reviewers: Kowshik Prakasam <kprakasam@confluent.io>, Jun Rao <junrao@gmail.com> (cherry picked from commit 3278090) Reviewers: #ldap_kafka_admins, kchandraprakash Reviewed By: #ldap_kafka_admins, kchandraprakash JIRA Issues: DKAFC-868 Differential Revision: https://code.uberinternal.com/D6303209
…and RemoteLogMetadataManager. (apache#10218) Summary: KAFKA-12368: Added inmemory implementations for RemoteStorageManager and RemoteLogMetadataManager. Added inmemory implementation for RemoteStorageManager and RemoteLogMetadataManager. A major part of inmemory RLMM will be used in the default RLMM implementation which will be based on topic storage. These will be used in unit tests for tiered storage. Added tests for both the implementations and their supported classes. This is part of tiered storage implementation, KIP-405. apache-reviewers: Kowshik Prakasam <kprakasam@confluent.io>, Jun Rao <junrao@gmail.com> (cherry picked from commit 3278090) Reviewers: #ldap_kafka_admins, kchandraprakash Reviewed By: #ldap_kafka_admins, kchandraprakash JIRA Issues: DKAFC-868 Differential Revision: https://code.uberinternal.com/D6303209
KAFKA-12368: Added inmemory implementations for RemoteStorageManager and RemoteLogMetadataManager.
This is part of tiered storage implementation, KIP-405.
Committer Checklist (excluded from commit message)