bump. Any ideas? We're seeing the same issue on 2.0 as well.
Thanks!
On Tue, Sep 3, 2013 at 2:20 PM, David Laube wrote:
> Hi All,
>
> After enabling encryption on our Cassandra 1.2.8 nodes, we receiving the
> error "Connection error: TSocket read 0 bytes" while attempting to use CQLsh
> to tal
t's almost 2,000 times faster (3 orders of magnitude difference)!
However, according to Aleksey Yeschenko, this performance problem has been
addressed in 2.0 beta 1 via
https://issues.apache.org/jira/browse/CASSANDRA-4693.
I'll reserve judgement until I can performance-test 2.0 beta 1
Well, it appears that this just isn't possible. I created CASSANDRA-5959
as a result. (Backstory + performance testing results are described in the
issue):
https://issues.apache.org/jira/browse/CASSANDRA-5959
--
Les Hazlewood | @lhazlewood
CTO, Stormpath | http://stormpath.com | @goStor
or of Astyanax for this particular
use case:
https://issues.apache.org/jira/browse/CASSANDRA-5959
Cheers,
--
Les Hazlewood | @lhazlewood
CTO, Stormpath | http://stormpath.com | @goStormpath | 888.391.5282
Hi all,
We're using a Cassandra table to store search results in a
table/column family that that look like this:
++-+-+-+
|| 0 | 1 | 2 | ...
++-+-+-+
| row_id | text... | text... | text... | ...
The
Thanks for the pointer Ryan!
Regards,
Les
Hi Dominic,
Thanks so much for providing this information. I was unaware of Cages and
this looks like it could be used effectively for certain things.
This is because Cassandra uses the timestamps of columns that have been
> written during reconciliation to determine which should be persisted wh
The issue has the fix version as 0.8.2, not 0.7.7. Is that incorrect?
Cheers,
Les
On Thu, Jun 23, 2011 at 10:41 AM, Chris Burroughs wrote:
>
>
> In the spirit of your re-formulated questions:
> - Read-before-write is a Cassandra anti-pattern, avoid it if at all
> possible.
>
This leads me to believe that Cassandra may not be a good idea for a primary
OLTP data store. For exa
>
> In the spirit of your re-formulated questions:
>> - Read-before-write is a Cassandra anti-pattern, avoid it if at all
>> possible.
>>
>
> This leads me to believe that Cassandra may not be a good idea for a
> primary OLTP data store. For example "only create a user object if email
> foo is no
On Thu, Jun 23, 2011 at 5:59 AM, Dominic Williams
wrote:
> Cassandra is a good system, but it has not reached version 1.0 yet, nor has
> HBase etc. It is cutting edge technology and therefore in practice you are
> unlikely to achieve five nines immediately - even if in theory with perfect
> planni
Great stuff Chris - thanks so much for the feedback!
Les
rote:
>
>
> On Wed, Jun 22, 2011 at 8:31 PM, Les Hazlewood wrote:
>
>> Hi Thoku,
>>
>> You were able to more concisely represent my intentions (and their
>> reasoning) in this thread than I was able to do so myself. Thanks!
>>
>> On Wed, Jun 22,
Hi Thoku,
You were able to more concisely represent my intentions (and their
reasoning) in this thread than I was able to do so myself. Thanks!
On Wed, Jun 22, 2011 at 5:14 PM, Thoku Hansen wrote:
> I think that Les's question was reasonable. Why *not* ask the community for
> the 'gotchas'?
>
Hi Scott,
First, let me say that this email was amazing - I'm always appreciative of
the time that anyone puts into mailing list replies, especially ones as
thorough, well-thought and articulated as this one. I'm a firm believer
that these types of replies reflect a strong and durable open-source
On Wed, Jun 22, 2011 at 4:35 PM, mcasandra wrote:
> might be helpful which varies from env to env. That's why I suggest look at
> the comments in cassandra.yaml and see which are applicable in your
> scenario. I learn something new everytime I read it.
>
Yep, and this was awesome - thanks very m
Yep, that was [2] on my existing list. Thanks very much for actually
addressing my question - it is greatly appreciated!
If anyone else has examples they'd like to share (like their own cron
techniques, or JVM settings and why, etc), I'd love to hear them!
Best regards,
Les
On Wed, Jun 22, 201
I have architected, built and been responsible for systems that support 4-5
9s for years. This discussion is not about how to do that generally. It
was intended to be about concrete techniques that have been found valuable
when deploying Cassandra in HA environments beyond what is documented in [
Forget the 5 9's - I apologize for even writing that. It was my shorthand
way of saying 'this can never go down'. I'm not asking for philosophical
advice - I've been doing large scale enterprise deployments for over 10
years. I 'get' the 'it depends' and 'do your homework' philosophy.
All I'm a
On Wed, Jun 22, 2011 at 4:11 PM, Peter Lin wrote:
> you have to use multiple data centers to really deliver 4 or 5 9's of
> service
>
We do, hence my question, as well as my choice of Cassandra :)
Best,
Les
>
> >
> > [1] http://www.datastax.com/docs/0.8/operations/index
> > [2] http://wiki.apache.org/cassandra/Operations
> >
>
> Well if they new some secret gotcha the dutiful cassandra operators of
> the world would update the wiki.
>
As I am new to the Cassandra community, I don't know how 'dutifull
I understand that every environment is different and it always 'depends' :)
But recommending settings and techniques based on an existing real
production environment (like the user's suggestion to run nodetool repair as
a regular cron job) is always a better starting point for a new Cassandra
eval
Just to be clear:
I understand that resources like [1] and [2] exist, and I've read them. I'm
just wondering if there are any 'gotchas' that might be missing from that
documentation that should be considered and if there are any recommendations
in addition to these documents.
Thanks,
Les
[1] h
I'm planning on using Cassandra as a product's core data store, and it is
imperative that it never goes down or loses data, even in the event of a
data center failure. This uptime requirement ("five nines": 99.999% uptime)
w/ WAN capabilities is largely what led me to choose Cassandra over other
N
24 matches
Mail list logo
