satishd opened a new pull request #10173:
URL: https://github.com/apache/kafka/pull/10173


   KAFKA-9548 Added SPIs and public classes/interfaces introduced in KIP-405 
for tiered storage feature in Kafka.
   
   KIP-405 introduces tiered storage feature in Kafka. With this feature, Kafka 
cluster is configured with two tiers of storage - local and remote. The local 
tier is the same as the current Kafka that uses the local disks on the Kafka 
brokers to store the log segments. The new remote tier uses systems, such as 
HDFS or S3 or other cloud storages to store the completed log segments. 
Consumers fetch the records stored in remote storage through the brokers with 
the existing protocol.
   
   We introduced a few SPIs for plugging in log/index store and remote log 
metadata store.
   
   This involves two parts
   1. Storing the actual data in remote storage like HDFS, S3, or other cloud 
stroages.
   2. Storing the metadata about where the remote segments are stored. The 
default implementation uses an internal Kafka topic.
   
   You can read KIP for more details at 
https://cwiki.apache.org/confluence/display/KAFKA/KIP-405%3A+Kafka+Tiered+Storage
   
   *More detailed description of your change,
   if necessary. The PR title and PR message become
   the squashed commit message, so use a separate
   comment to ping reviewers.*
   
   *Summary of testing strategy (including rationale)
   for the feature or bug fix. Unit and/or integration
   tests are expected for any behaviour change and
   system tests should be considered for larger changes.*
   
   ### Committer Checklist (excluded from commit message)
   - [ ] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)
   


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


Reply via email to