[Herddb-dev] New Diskless Cluster Mode v2

[Enrico Olivelli]

I will cut 0.19.0 tomorrow if no one objects.
Tests are passing, release early, release often !!

cheers
Enrico

Il giorno mar 1 set 2020 alle ore 17:24 Diego Salvi - Diennea <
diego.salvi at diennea.com> ha scritto:

> I think this is the right time to a new release.
>
> The official docker image can wait a next minor, it shouldn’t block the
> main release.
>
>
>
> Diego
>
>
>
>
>
> *Da: *<herddb-dev-bounces at mail4.mag-news.it> per conto di Enrico Olivelli
> <eolivelli at gmail.com>
> *Risposta: *Herddb developers <herddb-dev at mail4.mag-news.it>
> *Data: *martedì 1 settembre 2020 13:30
> *A: *Herddb developers <herddb-dev at lists.herddb.org>
> *Oggetto: *Re: [Herddb-dev] New Diskless Cluster Mode v2
>
>
>
> Hi all,
>
> we have committed option 2: "create default tablespace 'herd' with replica
> = '*', storageMode: bookkeeper and maxleaderinactivitytimeout=30 seconds"
> (but with 1 minute of timeout)
>
>
>
> I feel we are ready for cutting 0.19.0,
>
>
>
> I would like to see an official docker image, but we can make it for 0.19.1
>
>
>
> thoughts ?
>
>
>
>
>
> Enrico
>
>
>
> Il giorno lun 10 ago 2020 alle ore 15:28 Enrico Olivelli <
> eolivelli at gmail.com> ha scritto:
>
> Hi all,
>
> I have created a PR for Diskless Cluster Mode v2
>
> https://github.com/diennea/herddb/pull/676
>
>
>
> See the description for the details.
>
>
>
> This change introduces the ability to set '*' as 'replicas' for a
> tablespace, meaning that every node is automatically a good replica for the
> tablespace.
>
>
>
> This makes sense in Diskless Cluster Mode v2 because in that mode only one
> node works, the leader, and followers are stand-by only and do not store
> additional data.
>
>
>
> As a follow up I would like to work in two directions:
>
> - make the cluster mode: 'traditional' vs 'diskless' configurable
> per-tablespace and not per cluster, I would call it 'storageMode: file vs
> bookkeeper'
>
> - create default tablespace 'herd' with replica = '*', storageMode:
> bookkeeper and maxleaderinactivitytimeout=30 seconds
>
>
>
> with these two features the tablespace 'herd' will be always available,
> and this will ease working in an HerdDB cluster, because by default all of
> the queries, event the ones about metadata (systablespaces, sysnodes.....)
> are by default routed to the server for 'herd' tablespace.
>
>
>
> An alternative would be to add a new virtualtablespace, like  'metadata'
> that cannot contain tables and that it is assigned to every node
> (replica=*,  maxleaderinactivitytimeout=30 seconds)
>
>
>
> I would like to get this stuff in for 0.19.0, as I am preparing for the
> ApacheCon talk, and we need to be more userfriendly
>
>
>
> Thoughts ?
>
> Enrico
>
>
>
>
> ------------------------------
>
> CONFIDENTIALITY & PRIVACY NOTICE
> This e-mail (including any attachments) is strictly confidential and may
> also contain privileged information. If you are not the intended recipient
> you are not authorised to read, print, save, process or disclose this
> message. If you have received this message by mistake, please inform the
> sender immediately and destroy this e-mail, its attachments and any copies.
> Any use, distribution, reproduction or disclosure by any person other than
> the intended recipient is strictly prohibited and the person responsible
> may incur in penalties.
> The use of this e-mail is only for professional purposes; there is no
> guarantee that the correspondence towards this e-mail will be read only by
> the recipient, because, under certain circumstances, there may be a need to
> access this email by third subjects belonging to the Company.
> _______________________________________________
> herddb-dev mailing list
> herddb-dev at mail4.mag-news.it
> https://webmail4.mag-news.it/mailman/listinfo/herddb-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://webmail4.mag-news.it/pipermail/herddb-dev/attachments/20200901/b9fbb007/attachment.html>