I see, so there are no dedicated transient nodes, just other nodes that
function as witnesses.
This is still very exciting.
On Fri, Aug 31, 2018 at 1:49 PM Ariel Weisberg wrote:
> Hi,
>
> All nodes being the same (in terms of functionality) is something we
> wanted to stick with at least for n
Hi,
All nodes being the same (in terms of functionality) is something we wanted to
stick with at least for now. I think we want a design that changes the
operational, availability, and consistency story as little as possible when
it's completed.
Ariel
On Fri, Aug 31, 2018, at 2:27 PM, Carl Mue
Hi,
There are no transient nodes. All nodes are the same. If you have transient
replication enabled each node will transiently replicate some ranges instead of
fully replicating them.
Capacity requirements are reduced evenly across all nodes in the cluster.
Nodes are not temporarily transient
SOrry to spam this with two messages...
This ticket is also interesting because it is very close to what I imagined
a useful use case of RF4 / RF6: being basically RF3 + hot spare where you
marked (in the case of RF4) three nodes as primary and the fourth as hot
standby, which may be equivalent if
I put these questions on the ticket too... Sorry if some of them are
stupid.
So are (basically) these transient nodes basically serving as centralized
hinted handoff caches rather than having the hinted handoffs cluttering up
full replicas, especially nodes that have no concern for the token range
Hi all,
I wanted to give everyone an update on how development of Transient Replication
is going and where we are going to be as of 9/1. Blake Eggleston, Alex Petrov,
Benedict Elliott Smith, and myself have been working to get TR implemented for
4.0. Up to now we have avoided merging anything r
