unsubscribe
–Ben Standefer
Sent via Superhuman ( https://sprh.mn/?vip=benstande...@gmail.com )
Are there any plans or talks of adding SSL/encryption support between
Cassandra nodes? This would make setting up secure cross-country Cassandra
clusters much easier, without having to setup a secure overlay network.
MySQL supports this in it's replication.
-Ben
On Mon, Jul 12, 2010 at 11:23
useful w/o having encryption
for Thrift as well (in case a client has to fail over to the
cross-country Cassandra nodes). So using a secure VPN makes the most
sense to me.
On Tue, Jul 13, 2010 at 12:02 PM, Ben Standefer b...@simplegeo.com wrote:
Are there any plans or talks of adding SSL
Err, find it *unrealistic*
-Ben
On Tue, Jul 13, 2010 at 2:22 PM, Ben Standefer b...@simplegeo.com wrote:
Many apps would find it realistic or feasible to failover database
connections across the country (going from 1ms latency to ~90ms latency).
The scheme of failing over client database
Hi, my name is Larry and I am the Beverage Considerer for NUB Enterprises.
I am new to Coke and Digg, but I've already been reading Coke's nutrition
facts on the internet and even purchased a bottle the other day (it's
sitting in my office fridge right now). It looks like quite a promising
Joe,
(Disclaimer: I work here) Check out http://www.simplegeo.com, we're
building a horizontally scalable spatial database on top of Cassandra
along with geographic analytics, data provisioning, and hosting
services. Using us might be easier than hacking around in the weeds
with MongoDB.
Sorry
For various reasons I am required to deploy systems on Windows.
I don't think it would be difficult to argue the business case for running
Cassandra on Linux. It's still a young project and everybody in IRC and the
mailing list is running it on Linux. You should really re-think whatever
factors
In my opinion the #1 risk for corruption is user/client error with the
timestamps. Over time, Cassandra flushes data from memory to disks. After
it flushes to disk, Cassandra doesn't go back to delete or modify that data.
Because of this, deletes are performed by writing a tombstone to disk.
for the data directory so that we can more
easily snapshot our data (trusting that our AZ-aware EndPointSnitch),
while other AZs will continue ephemeral drives.
-Ben Standefer
On Thu, Jun 3, 2010 at 1:26 PM, Mike Subelsky m...@subelsky.com wrote:
Ben,
do you just keep the commit log on the ephemeral
/io_performance_on_ebs/
-Ben Standefer
On Thu, Jun 3, 2010 at 4:41 PM, Mike Subelsky m...@subelsky.com wrote:
Ben,
thanks for that, we may try that. I did find an AWS forum tidbit from
two years ago:
4 ephemeral stores striped together can give significantly higher
throughput for sequential writes
10 matches
Mail list logo
