> > >>> alexey.goncha...@gmail.com
>> > > > > > >>> > >:
>> > > > > > >>> >
>> > > > > > >>> >> Ivan,
>> > > > > > >>> >>
>>
7;s have a call to discuss the IEP. I have some
> > more
> > > > > > thoughts
> > > > > > >>> >> regarding how the replication infrastructure works with
> > > > > > >>> >> atomic/transactional caches, will put this
>> As for the protocol port - we will not be dealing with the
> > > > > concurrency
> > > > > >>> >> model if we choose this way, this is what I like about their
> > > code
> > > > > >>> >> structure. Essentially, t
gt; > > >>> >> model if we choose this way, this is what I like about their
> > code
> > > > >>> >> structure. Essentially, the raft module is a single-threaded
> > > > automata
> > > > >>> >> which
> > > > >&g
that should be sent and log entries that should be
> > > persisted.
> > > >>> >> Judging by the Rust port, it seems fairly straightforward. Will
> be
> > > >>> happy
> > > >>> >> to
> > > >>> >
t;>> >> Judging by the Rust port, it seems fairly straightforward. Will be
> > >>> happy
> > >>> >> to
> > >>> >> discuss this and other alternatives on the call as well.
> > >>> >>
> > >
this and other alternatives on the call as well.
> >>> >>
> >>> >> чт, 19 нояб. 2020 г. в 14:41, Ivan Daschinsky >:
> >>> >>
> >>> >> > > Any existing library that can be used to avoid re-implementing
> the
> &g
ting implementation to
>>> Java
>>> >> > Personally, I like this idea. Go libraries (either raft module of
>>> etcd
>>> >> or
>>> >> > serf by Hashicorp) are famous for clean code, good design,
>>> stability,
>>>
rhaps, porting the existing implementation to
>> Java
>> >> > Personally, I like this idea. Go libraries (either raft module of
>> etcd
>> >> or
>> >> > serf by Hashicorp) are famous for clean code, good design, stability,
>> >&
>> not
> >> > enormous size.
> >> > But, on other side, Go has different model for concurrency and porting
> >> > probably will not be so straightforward.
> >> >
> >> >
> >> >
> >> > чт, 19 нояб. 2020 г. в 13:48, Ivan Daschinsky :
> >> >
> &g
n other side, Go has different model for concurrency and porting
>> > probably will not be so straightforward.
>> >
>> >
>> >
>> > чт, 19 нояб. 2020 г. в 13:48, Ivan Daschinsky :
>> >
>> > > I'd suggest to discuss this IEP
t; > >
> > > чт, 19 нояб. 2020 г. в 13:47, Ivan Daschinsky :
> > >
> > >>
> > >>
> > >> -- Forwarded message -
> > >> От: Ivan Daschinsky
> > >> Date: чт, 19 нояб. 2020 г. в 13:02
> > >>
г. в 13:47, Ivan Daschinsky :
> >
> >>
> >>
> >> -- Forwarded message -
> >> От: Ivan Daschinsky
> >> Date: чт, 19 нояб. 2020 г. в 13:02
> >> Subject: Re: IEP-61 Technical discussion
> >> To: Alexey Goncharuk
&
:47, Ivan Daschinsky :
>
>>
>>
>> -- Forwarded message -
>> От: Ivan Daschinsky
>> Date: чт, 19 нояб. 2020 г. в 13:02
>> Subject: Re: IEP-61 Technical discussion
>> To: Alexey Goncharuk
>>
>>
>> Alexey, let's aris
I'd suggest to discuss this IEP and technical details in open ZOOM meeting.
чт, 19 нояб. 2020 г. в 13:47, Ivan Daschinsky :
>
>
> -- Forwarded message -
> От: Ivan Daschinsky
> Date: чт, 19 нояб. 2020 г. в 13:02
> Subject: Re: IEP-61 Technical discussion
-- Forwarded message -
От: Ivan Daschinsky
Date: чт, 19 нояб. 2020 г. в 13:02
Subject: Re: IEP-61 Technical discussion
To: Alexey Goncharuk
Alexey, let's arise another question. Specifically, how nodes initially
find each other (discovery) and how they detect failure
Following up the Ignite 3.0 scope/development approach threads, this is a
separate thread to discuss technical aspects of the IEP.
Let's reiterate one more time on the questions raised by Ivan and also see
if there are any other thoughts on the IEP:
- *Whether to deploy metastorage on a separa
17 matches
Mail list logo
