Re: Newbe?s question
Now now, we use subversion at OpenX and we are probably the only people who use Cassandra 0.3.0 in production, can't get more cutting edge than that :) -Anthony On Wed, Aug 26, 2009 at 07:31:48PM -0500, Jonathan Ellis wrote: > Off the top of my head, I can't think of any that actually use svn so > it's probably a moot point anyway. > > Subversion has practically zero mindshare now in the cutting edge > crowd (which most of cassandra's users come from, unsurprisingly :). > > -Jonathan > > On Wed, Aug 26, 2009 at 7:09 PM, Ian Holsman wrote: > > isn't there a way to use svn:external or svn:link to pull them in from their > > own repos? > > (not sure how legal it would be). > > On Aug 27, 2009, at 10:03 AM, Jonathan Ellis wrote: > > > >> I thought about that, but I really don't want Cassandra committers to > >> have to be in the business of updating them all when we make changes, > >> and having them in the repo creates that expectation even in contrib. > >> > >> On Wed, Aug 26, 2009 at 6:57 PM, Ian Holsman wrote: > >>> > >>> would it be worthwhile to start including these clients in the core > >>> codebase? in some kind of 'client' or 'contrib' directory? > >>> > >>> maybe even mentioning the 'popular' clients that people use in the readme > >>> (with links to them) would be good. > >>> > >>> On Aug 27, 2009, at 9:18 AM, Sal Fuentes wrote: > >>> > Just would like to say great job so far. > > On Wed, Aug 26, 2009 at 4:01 PM, Ian Eure wrote: > On Aug 25, 2009, at 2:46 PM, Drew Schleck wrote: > > For anyone using my branch of Lazyboy, Ian Eure pulled my work, > improved it, and more. You ought to switch back to his version. > > I'm doing some heavy refactoring all this week, to bring it up to > Cassandra trunk and simplify/genericize it wherever possible. I should > have > something to show in a day or two. > > Feel free to contact me if you have questions or requests. > > - Ian > > > > -- > Salvador Fuentes Jr. > 323-540-4SAL > >>> > >>> -- > >>> Ian Holsman > >>> i...@holsman.net > >>> > >>> > >>> > >>> > > > > -- > > Ian Holsman > > i...@holsman.net > > > > > > > > -- Anthony Molinaro
Re: TypeError: unhashable instance
For what it's worth, I ran the examples last night on 0.4 beta and it worked just fine. I of course used the example schema. On Wed, Aug 26, 2009 at 6:16 PM, wrote: > > Please try the record-refactor branch of Lazyboy. This will be merged to > master and 0.6.0 should be out in a week or so. > I haven't run the examples, but things are pretty much working for me. > > - Ian > -- Salvador Fuentes Jr.
Re: TypeError: unhashable instance
On Aug 26, 2009, at 5:42 PM, mobiledream...@gmail.com wrote: Resyncing to ian eure digg lazyboy - still not working same error persists Please try the record-refactor branch of Lazyboy. This will be merged to master and 0.6.0 should be out in a week or so. I haven't run the examples, but things are pretty much working for me. - Ian
Re: Newbe´s question
Don't call __hash__, there is no such method. On Aug 26, 2009, at 5:39 PM, mobiledream...@gmail.com wrote: any ideas on how 2 fix this? Traceback (most recent call last): File "/tmp/a.py", line 3, in print cassandra.ttypes.Column().__hash__() AttributeError: Column instance has no attribute '__hash__' #!/usr/bin/python import cassandra.ttypes print cassandra.ttypes.Column().__hash__() On Wed, Aug 26, 2009 at 5:13 PM, Evan Weaver wrote: "Clients" section in the README.txt seems best to me. Evan On Wed, Aug 26, 2009 at 5:09 PM, Ian Holsman wrote: > isn't there a way to use svn:external or svn:link to pull them in from their > own repos? > (not sure how legal it would be). > On Aug 27, 2009, at 10:03 AM, Jonathan Ellis wrote: > >> I thought about that, but I really don't want Cassandra committers to >> have to be in the business of updating them all when we make changes, >> and having them in the repo creates that expectation even in contrib. >> >> On Wed, Aug 26, 2009 at 6:57 PM, Ian Holsman wrote: >>> >>> would it be worthwhile to start including these clients in the core >>> codebase? in some kind of 'client' or 'contrib' directory? >>> >>> maybe even mentioning the 'popular' clients that people use in the readme >>> (with links to them) would be good. >>> >>> On Aug 27, 2009, at 9:18 AM, Sal Fuentes wrote: >>> Just would like to say great job so far. On Wed, Aug 26, 2009 at 4:01 PM, Ian Eure wrote: On Aug 25, 2009, at 2:46 PM, Drew Schleck wrote: For anyone using my branch of Lazyboy, Ian Eure pulled my work, improved it, and more. You ought to switch back to his version. I'm doing some heavy refactoring all this week, to bring it up to Cassandra trunk and simplify/genericize it wherever possible. I should have something to show in a day or two. Feel free to contact me if you have questions or requests. - Ian -- Salvador Fuentes Jr. 323-540-4SAL >>> >>> -- >>> Ian Holsman >>> i...@holsman.net >>> >>> >>> >>> > > -- > Ian Holsman > i...@holsman.net > > > > -- Evan Weaver -- Bidegg worlds best auction site http://bidegg.com
Re: Newbe´s question
On Wed, 2009-08-26 at 17:33 -0700, Chris Goffinet wrote: > Don't know what you're talking about, I am still rolling with CVS. Oh, what a twisted sense of humor you have Chris. -- Eric Evans eev...@rackspace.com
TypeError: unhashable instance
Resyncing to ian eure digg lazyboy - still not working same error persists *code*: http://pastie.org/596171 *Error* python columnfamily.py {'table': 'Keyspace1', 'superkey': None, 'key': 'ef03418890d14d55ab5f919cf9c62184', 'family': 'Standard1', 'supercol': None} {'username': 'ieure', 'email': 'i...@digg.com'} True Traceback (most recent call last): File "columnfamily.py", line 65, in u.save() # -> {'username': 'ieure', 'email': 'i...@digg.com'} File "/home/mark/work/common/lazyboy/columnfamily.py", line 127, in save self.load(self.pk.key) File "/home/mark/work/common/lazyboy/columnfamily.py", line 92, in load self._clean() File "/home/mark/work/common/lazyboy/columnfamily.py", line 46, in _clean map(self.__delitem__, self.keys()) File "/home/mark/work/common/lazyboy/columnfamily.py", line 86, in __delitem__ self._deleted[self._columns[item]] = True TypeError: unhashable instance On Wed, Aug 26, 2009 at 5:10 PM, Eric Evans wrote: > On Thu, 2009-08-27 at 09:57 +1000, Ian Holsman wrote: > > would it be worthwhile to start including these clients in the core > > codebase? in some kind of 'client' or 'contrib' directory? > > IMO, it would be better for the clients and those working on them to > continue managing them as separate projects outside of Cassandra's > code-base, (flexibility on choice of committers, vcs/tools, release > cycles, licensing, etc). > > > maybe even mentioning the 'popular' clients that people use in the > > readme (with links to them) would be good. > > Yeah, this is probably a good idea. Either README.txt or a > (prominent )page on the wiki (which I guess would be easier to keep to > date). > > -- > Eric Evans > eev...@rackspace.com > > -- Bidegg worlds best auction site http://bidegg.com
Re: Newbe´s question
any ideas on how 2 fix this? Traceback (most recent call last): File "/tmp/a.py", line 3, in print cassandra.ttypes.Column().__hash__() AttributeError: Column instance has no attribute '__hash__' * #!/usr/bin/python import cassandra.ttypes print cassandra.ttypes.Column().__hash__() * On Wed, Aug 26, 2009 at 5:13 PM, Evan Weaver wrote: > "Clients" section in the README.txt seems best to me. > > Evan > > On Wed, Aug 26, 2009 at 5:09 PM, Ian Holsman wrote: > > isn't there a way to use svn:external or svn:link to pull them in from > their > > own repos? > > (not sure how legal it would be). > > On Aug 27, 2009, at 10:03 AM, Jonathan Ellis wrote: > > > >> I thought about that, but I really don't want Cassandra committers to > >> have to be in the business of updating them all when we make changes, > >> and having them in the repo creates that expectation even in contrib. > >> > >> On Wed, Aug 26, 2009 at 6:57 PM, Ian Holsman wrote: > >>> > >>> would it be worthwhile to start including these clients in the core > >>> codebase? in some kind of 'client' or 'contrib' directory? > >>> > >>> maybe even mentioning the 'popular' clients that people use in the > readme > >>> (with links to them) would be good. > >>> > >>> On Aug 27, 2009, at 9:18 AM, Sal Fuentes wrote: > >>> > Just would like to say great job so far. > > On Wed, Aug 26, 2009 at 4:01 PM, Ian Eure wrote: > On Aug 25, 2009, at 2:46 PM, Drew Schleck wrote: > > For anyone using my branch of Lazyboy, Ian Eure pulled my work, > improved it, and more. You ought to switch back to his version. > > I'm doing some heavy refactoring all this week, to bring it up to > Cassandra trunk and simplify/genericize it wherever possible. I should > have > something to show in a day or two. > > Feel free to contact me if you have questions or requests. > > - Ian > > > > -- > Salvador Fuentes Jr. > 323-540-4SAL > >>> > >>> -- > >>> Ian Holsman > >>> i...@holsman.net > >>> > >>> > >>> > >>> > > > > -- > > Ian Holsman > > i...@holsman.net > > > > > > > > > > > > -- > Evan Weaver > -- Bidegg worlds best auction site http://bidegg.com
Re: Newbe´s question
Don't know what you're talking about, I am still rolling with CVS. -Chris On Aug 26, 2009, at 5:31 PM, Jonathan Ellis wrote: Off the top of my head, I can't think of any that actually use svn so it's probably a moot point anyway. Subversion has practically zero mindshare now in the cutting edge crowd (which most of cassandra's users come from, unsurprisingly :). -Jonathan On Wed, Aug 26, 2009 at 7:09 PM, Ian Holsman wrote: isn't there a way to use svn:external or svn:link to pull them in from their own repos? (not sure how legal it would be). On Aug 27, 2009, at 10:03 AM, Jonathan Ellis wrote: I thought about that, but I really don't want Cassandra committers to have to be in the business of updating them all when we make changes, and having them in the repo creates that expectation even in contrib. On Wed, Aug 26, 2009 at 6:57 PM, Ian Holsman wrote: would it be worthwhile to start including these clients in the core codebase? in some kind of 'client' or 'contrib' directory? maybe even mentioning the 'popular' clients that people use in the readme (with links to them) would be good. On Aug 27, 2009, at 9:18 AM, Sal Fuentes wrote: Just would like to say great job so far. On Wed, Aug 26, 2009 at 4:01 PM, Ian Eure wrote: On Aug 25, 2009, at 2:46 PM, Drew Schleck wrote: For anyone using my branch of Lazyboy, Ian Eure pulled my work, improved it, and more. You ought to switch back to his version. I'm doing some heavy refactoring all this week, to bring it up to Cassandra trunk and simplify/genericize it wherever possible. I should have something to show in a day or two. Feel free to contact me if you have questions or requests. - Ian -- Salvador Fuentes Jr. 323-540-4SAL -- Ian Holsman i...@holsman.net -- Ian Holsman i...@holsman.net
Re: Newbe´s question
Off the top of my head, I can't think of any that actually use svn so it's probably a moot point anyway. Subversion has practically zero mindshare now in the cutting edge crowd (which most of cassandra's users come from, unsurprisingly :). -Jonathan On Wed, Aug 26, 2009 at 7:09 PM, Ian Holsman wrote: > isn't there a way to use svn:external or svn:link to pull them in from their > own repos? > (not sure how legal it would be). > On Aug 27, 2009, at 10:03 AM, Jonathan Ellis wrote: > >> I thought about that, but I really don't want Cassandra committers to >> have to be in the business of updating them all when we make changes, >> and having them in the repo creates that expectation even in contrib. >> >> On Wed, Aug 26, 2009 at 6:57 PM, Ian Holsman wrote: >>> >>> would it be worthwhile to start including these clients in the core >>> codebase? in some kind of 'client' or 'contrib' directory? >>> >>> maybe even mentioning the 'popular' clients that people use in the readme >>> (with links to them) would be good. >>> >>> On Aug 27, 2009, at 9:18 AM, Sal Fuentes wrote: >>> Just would like to say great job so far. On Wed, Aug 26, 2009 at 4:01 PM, Ian Eure wrote: On Aug 25, 2009, at 2:46 PM, Drew Schleck wrote: For anyone using my branch of Lazyboy, Ian Eure pulled my work, improved it, and more. You ought to switch back to his version. I'm doing some heavy refactoring all this week, to bring it up to Cassandra trunk and simplify/genericize it wherever possible. I should have something to show in a day or two. Feel free to contact me if you have questions or requests. - Ian -- Salvador Fuentes Jr. 323-540-4SAL >>> >>> -- >>> Ian Holsman >>> i...@holsman.net >>> >>> >>> >>> > > -- > Ian Holsman > i...@holsman.net > > > >
Re: Newbe´s question
the problem is README changes far too infrequently from the pov of someone who just uses official releases. we have a list here: http://wiki.apache.org/cassandra/ClientExamples which I have deliberately left incomplete (only projects with commits in the last month or so, since nothing else has a prayer of working). moving to its own page is fine with me. On Wed, Aug 26, 2009 at 7:13 PM, Evan Weaver wrote: > "Clients" section in the README.txt seems best to me. > > Evan > > On Wed, Aug 26, 2009 at 5:09 PM, Ian Holsman wrote: >> isn't there a way to use svn:external or svn:link to pull them in from their >> own repos? >> (not sure how legal it would be). >> On Aug 27, 2009, at 10:03 AM, Jonathan Ellis wrote: >> >>> I thought about that, but I really don't want Cassandra committers to >>> have to be in the business of updating them all when we make changes, >>> and having them in the repo creates that expectation even in contrib. >>> >>> On Wed, Aug 26, 2009 at 6:57 PM, Ian Holsman wrote: would it be worthwhile to start including these clients in the core codebase? in some kind of 'client' or 'contrib' directory? maybe even mentioning the 'popular' clients that people use in the readme (with links to them) would be good. On Aug 27, 2009, at 9:18 AM, Sal Fuentes wrote: > Just would like to say great job so far. > > On Wed, Aug 26, 2009 at 4:01 PM, Ian Eure wrote: > On Aug 25, 2009, at 2:46 PM, Drew Schleck wrote: > > For anyone using my branch of Lazyboy, Ian Eure pulled my work, > improved it, and more. You ought to switch back to his version. > > I'm doing some heavy refactoring all this week, to bring it up to > Cassandra trunk and simplify/genericize it wherever possible. I should > have > something to show in a day or two. > > Feel free to contact me if you have questions or requests. > > - Ian > > > > -- > Salvador Fuentes Jr. > 323-540-4SAL -- Ian Holsman i...@holsman.net >> >> -- >> Ian Holsman >> i...@holsman.net >> >> >> >> > > > > -- > Evan Weaver >
Re: Newbe´s question
"Clients" section in the README.txt seems best to me. Evan On Wed, Aug 26, 2009 at 5:09 PM, Ian Holsman wrote: > isn't there a way to use svn:external or svn:link to pull them in from their > own repos? > (not sure how legal it would be). > On Aug 27, 2009, at 10:03 AM, Jonathan Ellis wrote: > >> I thought about that, but I really don't want Cassandra committers to >> have to be in the business of updating them all when we make changes, >> and having them in the repo creates that expectation even in contrib. >> >> On Wed, Aug 26, 2009 at 6:57 PM, Ian Holsman wrote: >>> >>> would it be worthwhile to start including these clients in the core >>> codebase? in some kind of 'client' or 'contrib' directory? >>> >>> maybe even mentioning the 'popular' clients that people use in the readme >>> (with links to them) would be good. >>> >>> On Aug 27, 2009, at 9:18 AM, Sal Fuentes wrote: >>> Just would like to say great job so far. On Wed, Aug 26, 2009 at 4:01 PM, Ian Eure wrote: On Aug 25, 2009, at 2:46 PM, Drew Schleck wrote: For anyone using my branch of Lazyboy, Ian Eure pulled my work, improved it, and more. You ought to switch back to his version. I'm doing some heavy refactoring all this week, to bring it up to Cassandra trunk and simplify/genericize it wherever possible. I should have something to show in a day or two. Feel free to contact me if you have questions or requests. - Ian -- Salvador Fuentes Jr. 323-540-4SAL >>> >>> -- >>> Ian Holsman >>> i...@holsman.net >>> >>> >>> >>> > > -- > Ian Holsman > i...@holsman.net > > > > -- Evan Weaver
Re: Newbe´s question
isn't there a way to use svn:external or svn:link to pull them in from their own repos? (not sure how legal it would be). On Aug 27, 2009, at 10:03 AM, Jonathan Ellis wrote: I thought about that, but I really don't want Cassandra committers to have to be in the business of updating them all when we make changes, and having them in the repo creates that expectation even in contrib. On Wed, Aug 26, 2009 at 6:57 PM, Ian Holsman wrote: would it be worthwhile to start including these clients in the core codebase? in some kind of 'client' or 'contrib' directory? maybe even mentioning the 'popular' clients that people use in the readme (with links to them) would be good. On Aug 27, 2009, at 9:18 AM, Sal Fuentes wrote: Just would like to say great job so far. On Wed, Aug 26, 2009 at 4:01 PM, Ian Eure wrote: On Aug 25, 2009, at 2:46 PM, Drew Schleck wrote: For anyone using my branch of Lazyboy, Ian Eure pulled my work, improved it, and more. You ought to switch back to his version. I'm doing some heavy refactoring all this week, to bring it up to Cassandra trunk and simplify/genericize it wherever possible. I should have something to show in a day or two. Feel free to contact me if you have questions or requests. - Ian -- Salvador Fuentes Jr. 323-540-4SAL -- Ian Holsman i...@holsman.net -- Ian Holsman i...@holsman.net
Re: Newbe´s question
On Thu, 2009-08-27 at 09:57 +1000, Ian Holsman wrote: > would it be worthwhile to start including these clients in the core > codebase? in some kind of 'client' or 'contrib' directory? IMO, it would be better for the clients and those working on them to continue managing them as separate projects outside of Cassandra's code-base, (flexibility on choice of committers, vcs/tools, release cycles, licensing, etc). > maybe even mentioning the 'popular' clients that people use in the > readme (with links to them) would be good. Yeah, this is probably a good idea. Either README.txt or a (prominent )page on the wiki (which I guess would be easier to keep to date). -- Eric Evans eev...@rackspace.com
Re: Newbe´s question
I thought about that, but I really don't want Cassandra committers to have to be in the business of updating them all when we make changes, and having them in the repo creates that expectation even in contrib. On Wed, Aug 26, 2009 at 6:57 PM, Ian Holsman wrote: > would it be worthwhile to start including these clients in the core > codebase? in some kind of 'client' or 'contrib' directory? > > maybe even mentioning the 'popular' clients that people use in the readme > (with links to them) would be good. > > On Aug 27, 2009, at 9:18 AM, Sal Fuentes wrote: > >> Just would like to say great job so far. >> >> On Wed, Aug 26, 2009 at 4:01 PM, Ian Eure wrote: >> On Aug 25, 2009, at 2:46 PM, Drew Schleck wrote: >> >> For anyone using my branch of Lazyboy, Ian Eure pulled my work, >> improved it, and more. You ought to switch back to his version. >> >> I'm doing some heavy refactoring all this week, to bring it up to >> Cassandra trunk and simplify/genericize it wherever possible. I should have >> something to show in a day or two. >> >> Feel free to contact me if you have questions or requests. >> >> - Ian >> >> >> >> -- >> Salvador Fuentes Jr. >> 323-540-4SAL > > -- > Ian Holsman > i...@holsman.net > > > >
Re: Newbe´s question
would it be worthwhile to start including these clients in the core codebase? in some kind of 'client' or 'contrib' directory? maybe even mentioning the 'popular' clients that people use in the readme (with links to them) would be good. On Aug 27, 2009, at 9:18 AM, Sal Fuentes wrote: Just would like to say great job so far. On Wed, Aug 26, 2009 at 4:01 PM, Ian Eure wrote: On Aug 25, 2009, at 2:46 PM, Drew Schleck wrote: For anyone using my branch of Lazyboy, Ian Eure pulled my work, improved it, and more. You ought to switch back to his version. I'm doing some heavy refactoring all this week, to bring it up to Cassandra trunk and simplify/genericize it wherever possible. I should have something to show in a day or two. Feel free to contact me if you have questions or requests. - Ian -- Salvador Fuentes Jr. 323-540-4SAL -- Ian Holsman i...@holsman.net
Re: Newbe´s question
Just would like to say great job so far. On Wed, Aug 26, 2009 at 4:01 PM, Ian Eure wrote: > On Aug 25, 2009, at 2:46 PM, Drew Schleck wrote: > > For anyone using my branch of Lazyboy, Ian Eure pulled my work, >> improved it, and more. You ought to switch back to his version. >> >> I'm doing some heavy refactoring all this week, to bring it up to > Cassandra trunk and simplify/genericize it wherever possible. I should have > something to show in a day or two. > > Feel free to contact me if you have questions or requests. > > - Ian > -- Salvador Fuentes Jr. 323-540-4SAL
Re: Newbe´s question
On Aug 25, 2009, at 2:46 PM, Drew Schleck wrote: For anyone using my branch of Lazyboy, Ian Eure pulled my work, improved it, and more. You ought to switch back to his version. I'm doing some heavy refactoring all this week, to bring it up to Cassandra trunk and simplify/genericize it wherever possible. I should have something to show in a day or two. Feel free to contact me if you have questions or requests. - Ian
Re: Server cannot startup after shutdown
On Wed, Aug 26, 2009 at 12:26 PM, Brian Frank Cooper wrote: >> Is the commitlog small enough that you can gzip it and attach to JIRA >> (10 MB limit)? > > /var/cassandra/commitlog has 215 files totaling about 28 GB. Most are 134 MB, > the last one is 6MB. Which one would be useful to you? Can you update to trunk and re-run recovery with log level set to DEBUG? It will log the file it is in like this: DEBUG - Replaying /var/lib/cassandra/commitlog/CommitLog-1251137387800.log starting at 117 then before it errors out the last entry like DEBUG - Reading mutation at 666 > That's the curious thing; there were no writes in progress. In fact, my > experiment had finished about 24 hours before, and there was no load in > between, and then I shut down and still couldn't restart. I figured all the > writes would have committed by then. Must be a different bug, then. Thanks for finding it for us! :) -Jonathan
Re: Server cannot startup after shutdown
On Wed, Aug 19, 2009 at 9:46 PM, Jonathan Ellis wrote: > The OOM puzzles me a little; I'm not sure how it could be unable to > replay a mutation that it was able to write to the commitlog in the > first place. Ah, I think I know: if a compaction starts during recovery, that could suck up a bunch of memory.
RE: Server cannot startup after shutdown
> Is the commitlog small enough that you can gzip it and attach to JIRA > (10 MB limit)? /var/cassandra/commitlog has 215 files totaling about 28 GB. Most are 134 MB, the last one is 6MB. Which one would be useful to you? > Right, but you can still have an incomplete write in progress if you > shut down while writes are still happening. That's the curious thing; there were no writes in progress. In fact, my experiment had finished about 24 hours before, and there was no load in between, and then I shut down and still couldn't restart. I figured all the writes would have committed by then. thanks... brian
Re: Cassandra hardware setup
On Tue, Aug 25, 2009 at 7:07 PM, Scott Chacon wrote: > We're playing with Cassandra and would like to get a test cluster > setup for evaluation. I've been playing with it on my laptop and EC2, > which are the resources easily available to me, but not that close to > what I would be using in a production environment. Yeah, EC2 is io hell. Jason at slicehost thinks their VMs and cloud servers' should post better numbers, fwiw, but it's still going to be best to run on non-virtualized hardware. > What would be an ideal machine setup for a Cassandra node? At least > two separate physical disks, one for the commit log and another for > the data, no RAID, 8-16G memory? (I think that's what Evan recommended > in his blog post) Right. Right now you don't get a huge win on writes from going over commitlog disk + 1 disk per heavily-written columnfamily, but if you can get to 3 or 4 without much extra cost (e.g. staying in 1U) it will help read seeks linearly, on average. So more is better. If you do have multiple data disks, I would expect JBOD to work better than raid0-ing things. (Mostly a wash on writes, but better read performance.) But I don't know if anyone has actually tested this. Digg is running on 16GB machines with a 10 GB heap size, which you can set in cassandra.in.sh. Cassandra defaults are tuned so that you can test things out on a 1GB heap without OOM-ing. Look in the peformance section; the main ones are MemtableSizeInMB MemtableObjectCountInMillions If you are also using a 10GB heap then you can just multiply these by 10 as a first step. If you are using 8 cores you probably want to double ConcurrentReads too. -Jonathan
Re: Server cannot startup after shutdown
On Wed, Aug 26, 2009 at 1:03 AM, Brian Frank Cooper wrote: > Hi, Jonathan, > > I have been trying to shutdown and restart Cassandra again this morning. I > still get the malformed entry bug (which you say below your patch fixes.) I > also get: > > ERROR - Exception encountered during startup. > java.lang.NegativeArraySizeException That could be a related problem. Or it might be a different bug. :) Is the commitlog small enough that you can gzip it and attach to JIRA (10 MB limit)? > No out of memory error this time, though. > > I'm also curious about your comment "I introduced a regression where it > couldn't handle the last entry in the commitlog being incomplete." Does the > last entry in the commit log being incomplete mean that the last update or > set of updates are not fully committed to the log? And therefore they are > lost? I thought since I had set "true" that > all updates would be fully flushed before returning to the caller. Right, but you can still have an incomplete write in progress if you shut down while writes are still happening. -Jonathan