Re: Making RF4 useful aka primary and secondary ranges

2018-03-15 Thread Carl Mueller
Close. I'm suggesting that if you have RF4 or 5 or 6, you get to designate a subset of three replicas that are strongly preferred. From this "virtual subset/datacenter" if you do QUORUM against that subset, it just does n/2+1 of the subset. Updates are still sent to the non-primary replicas, and

RE: NVIDIA TESLA: The World's Most Advance Data Center GPU's for accelerating demanding HPC workloads

2018-03-15 Thread Kenneth Brotman
It's off topic if there aren't any C* uses but I wasn't (still not sure) there aren't. Maybe you're missing out. -Original Message- From: Jason Brown [mailto:jasedbr...@gmail.com] Sent: Thursday, March 15, 2018 10:26 AM To: dev@cassandra.apache.org Subject: Re: NVIDIA TESLA: The World's

Re: NVIDIA TESLA: The World's Most Advance Data Center GPU's for accelerating demanding HPC workloads

2018-03-15 Thread Jason Brown
All, This is completely OFF-TOPIC for this mailing list. Please stop. -Jason On Thu, Mar 15, 2018 at 10:09 AM, daemeon reiydelle wrote: > Not so sure they are C* relevant, I build (100's of GPU enabled node) HPC's > that use them for ML, AI, Graph analytics, etc. with the

Re: NVIDIA TESLA: The World's Most Advance Data Center GPU's for accelerating demanding HPC workloads

2018-03-15 Thread daemeon reiydelle
Not so sure they are C* relevant, I build (100's of GPU enabled node) HPC's that use them for ML, AI, Graph analytics, etc. with the sources in C* or more typically Hadoop/EMR data. <==> "Who do you think made the first stone spear? The Asperger guy. If you get rid of the autism genetics,

RE: A JIRA proposing a seperate repository for the online documentation

2018-03-15 Thread Kenneth Brotman
Well pickle my cucumbers Jon! It's good to know that you have experience with Hugo, see it as a good fit and that all has been well. I look forward to the jira epic! How exactly does the group make such a decision: Call for final discussion? Call for vote? Wait for the PMC to vote?

Re: A JIRA proposing a seperate repository for the online documentation

2018-03-15 Thread Jon Haddad
Murukesh is correct on a very useable, pretty standard process of multi-versioned docs. I’ll put my thoughts in a JIRA epic tonight. I’ll be a multi-phase process. Also correct in that I’d like us to move to Hugo for the site, I’d like us to have a unified system between the site & the docs,

Re: A JIRA proposing a seperate repository for the online documentation

2018-03-15 Thread Murukesh Mohanan
On Fri, Mar 16, 2018 at 0:19 Kenneth Brotman wrote: > Help me out here. I could have had a website with support for more than > one version done several different ways by now. > > A website with several versions of documentation is going to have > sub-directories

NVIDIA TESLA: The World's Most Advance Data Center GPU's for accelerating demanding HPC workloads

2018-03-15 Thread Kenneth Brotman
I see things like this https://www.nvidia.com/en-us/data-center/tesla/#section3 as something I might be using in things I help build. Does anyone have any experience with them? Kenneth Brotman

RE: A JIRA proposing a seperate repository for the online documentation

2018-03-15 Thread Kenneth Brotman
Help me out here. I could have had a website with support for more than one version done several different ways by now. A website with several versions of documentation is going to have sub-directories for each version of documentation obviously. I've offered to create those

Re: A JIRA proposing a seperate repository for the online documentation

2018-03-15 Thread Eric Evans
On Thu, Mar 15, 2018 at 4:58 AM, Rahul Singh wrote: > > I don’t understand why it’s so complicated. In tree docs are as good as any. > All the old docs are there in the version control system. > > All we need to is a) generate docs for old versions b) improve user

Re: A JIRA proposing a seperate repository for the online documentation

2018-03-15 Thread Rahul Singh
I don’t understand why it’s so complicated. In tree docs are as good as any. All the old docs are there in the version control system. All we need to is a) generate docs for old versions b) improve user experience on the site by having it clearly laid out what is latest vs. old docs. and c)