n 14, 2020 at 9:06 AM Habib Nahas wrote:
>
> > Any chance of an update on the KIP? We are interested in seeing this move
> > forward.
> >
> > Thanks,
> > Habib
> > Sr SDE, AWS
> >
> > On Wed, Dec 18, 2019, at 3:27 PM, Habib Nahas wrote:
> &
Any chance of an update on the KIP? We are interested in seeing this move
forward.
Thanks,
Habib
Sr SDE, AWS
On Wed, Dec 18, 2019, at 3:27 PM, Habib Nahas wrote:
> Thanks Sean. Look forward to the updated KIP.
>
> Regards,
> Habib
>
> On Fri, Dec 13, 2019, at 6:22 AM,
Time {
> > ZoneId zoneSingapore = ZoneId.of("Asia/Singapore");
> > Clock clockSingapore = Clock.system(zoneSingapore);
> >
> > @Override
> > public long getWallClockTime(TopicPartition tp) {
> > return clockSingapore.instant.getEpochSecond();
> > }
> >
> > ...
Hi Sean,
Thanks for the KIP.
As I understand it users are free to set their own timestamp on ProducerRecord.
What is the recommendation for the proposed metric in a scenario where the user
sets this timestamp in timezone A and consumes the record in timezone B. Its
not clear to me if a
log
> indexes for older segments. Follower replicas will not replicate the
> data beyond local log retention. So, the data that is out of local log
> retention period/size will be fetched from the remote tier.
>
> Thanks,
> Satish.
>
> On Thu, Jul 25, 2019 at 6:01 AM Habib Nahas
Hi,
Under the proposed definition of RemoteTier, would it be possible to have an
implementation that transfers older log segments to a slower storage tier, but
one that is still local?
Examples of slower local(ie mounted locally) tiers being HDDs vs SSDs, or NFS
volumes.
Let me know if I"m
