Re: [VOTE] Release Apache Cassandra 1.1.0-beta2
Including my own, I count 3 binding +1's, one other +1 and no -1's. The vote passes, I'll get the artifacts published. -- Sylvain On Fri, Mar 23, 2012 at 7:00 PM, Brandon Williams wrote: > +1 > > On Fri, Mar 23, 2012 at 5:26 AM, Sylvain Lebresne > wrote: >> There is has been quite some changes since the beta1[1] (including some non >> trivial ones) and so while we still have a few outstanding small issues that >> may need to be addressed before calling for a release candidate, a new beta >> seems like the reasonable thing to do. I thus propose the following artifacts >> for release as 1.1.0-beta2. >> >> sha1: 643d18af24574d82ba565f6fe6482225f89f5d18 >> Git: >> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.1.0-beta2-tentative >> Artifacts: >> https://repository.apache.org/content/repositories/orgapachecassandra-104/org/apache/cassandra/apache-cassandra/1.1.0-beta2/ >> Staging repository: >> https://repository.apache.org/content/repositories/orgapachecassandra-104/ >> >> The artifacts as well as the debian package are also available here: >> http://people.apache.org/~slebresne/ >> >> The vote will be open for 72 hours (longer if needed). >> >> [1]: http://goo.gl/yNMo3 (CHANGES.txt) >> [2]: http://goo.gl/2AFuM (NEWS.txt)
OoM querying very wide-row in CLI
Today, running 1.0.7, we saw a node crash with an OutOfMemory. We have a single row with ~10million columns in it. (using it as an index) Accidentally, we attempted to list the CF in CLI that had the wide-row. This caused the CLI to hang and then eventually crashed Cassandra with an OoM. I know this is a case of "If it hurts when you do that, don't do that", but we may want to better protect against it in the CLI and/or the DB. I know we limit row counts on lists in CLI. Do we also limit column counts? If not, I don't mind submitting a patch for this. let me know, brian -- Brian ONeill Lead Architect, Health Market Science (http://healthmarketscience.com) mobile:215.588.6024 blog: http://weblogs.java.net/blog/boneill42/ blog: http://brianoneill.blogspot.com/
Re: OoM querying very wide-row in CLI
I believe we added support for specifying a column range to the cli recently. I don't know if there is a default limit. On Tue, Mar 27, 2012 at 8:40 PM, Brian O'Neill wrote: > Today, running 1.0.7, we saw a node crash with an OutOfMemory. > We have a single row with ~10million columns in it. (using it as an index) > Accidentally, we attempted to list the CF in CLI that had the wide-row. > This caused the CLI to hang and then eventually crashed Cassandra with an > OoM. > > I know this is a case of "If it hurts when you do that, don't do that", but > we may want to better protect against it in the CLI and/or the DB. I know > we limit row counts on lists in CLI. Do we also limit column counts? If > not, I don't mind submitting a patch for this. > > let me know, > brian > > -- > Brian ONeill > Lead Architect, Health Market Science (http://healthmarketscience.com) > mobile:215.588.6024 > blog: http://weblogs.java.net/blog/boneill42/ > blog: http://brianoneill.blogspot.com/ -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
Re: OoM querying very wide-row in CLI
10-4. I'll see if I can track it down and submit a pull request that specifies a default if one does not exist. -brian Brian O'Neill Lead Architect, Software Development Health Market Science | 2700 Horizon Drive | King of Prussia, PA 19406 p: 215.588.6024blog: http://weblogs.java.net/blog/boneill42/ blog: http://brianoneill.blogspot.com/ On 3/27/12 9:45 PM, "Jonathan Ellis" wrote: >I believe we added support for specifying a column range to the cli >recently. I don't know if there is a default limit. > >On Tue, Mar 27, 2012 at 8:40 PM, Brian O'Neill >wrote: >> Today, running 1.0.7, we saw a node crash with an OutOfMemory. >> We have a single row with ~10million columns in it. (using it as an >>index) >> Accidentally, we attempted to list the CF in CLI that had the wide-row. >> This caused the CLI to hang and then eventually crashed Cassandra with >>an >> OoM. >> >> I know this is a case of "If it hurts when you do that, don't do that", >>but >> we may want to better protect against it in the CLI and/or the DB. I >>know >> we limit row counts on lists in CLI. Do we also limit column counts? >>If >> not, I don't mind submitting a patch for this. >> >> let me know, >> brian >> >> -- >> Brian ONeill >> Lead Architect, Health Market Science (http://healthmarketscience.com) >> mobile:215.588.6024 >> blog: http://weblogs.java.net/blog/boneill42/ >> blog: http://brianoneill.blogspot.com/ > > > >-- >Jonathan Ellis >Project Chair, Apache Cassandra >co-founder of DataStax, the source for professional Cassandra support >http://www.datastax.com
Re: OoM querying very wide-row in CLI
Here she is: https://github.com/apache/cassandra/pull/8 Verified functionally with the attached data script. -brian On Tue, Mar 27, 2012 at 9:49 PM, Brian O'Neill wrote: > 10-4. I'll see if I can track it down and submit a pull request that > specifies a default if one does not exist. > > -brian > > > Brian O'Neill > Lead Architect, Software Development > Health Market Science | 2700 Horizon Drive | King of Prussia, PA 19406 > p: 215.588.6024blog: http://weblogs.java.net/blog/boneill42/ > blog: http://brianoneill.blogspot.com/ > > > > > > > > On 3/27/12 9:45 PM, "Jonathan Ellis" wrote: > > >I believe we added support for specifying a column range to the cli > >recently. I don't know if there is a default limit. > > > >On Tue, Mar 27, 2012 at 8:40 PM, Brian O'Neill > >wrote: > >> Today, running 1.0.7, we saw a node crash with an OutOfMemory. > >> We have a single row with ~10million columns in it. (using it as an > >>index) > >> Accidentally, we attempted to list the CF in CLI that had the wide-row. > >> This caused the CLI to hang and then eventually crashed Cassandra with > >>an > >> OoM. > >> > >> I know this is a case of "If it hurts when you do that, don't do that", > >>but > >> we may want to better protect against it in the CLI and/or the DB. I > >>know > >> we limit row counts on lists in CLI. Do we also limit column counts? > >>If > >> not, I don't mind submitting a patch for this. > >> > >> let me know, > >> brian > >> > >> -- > >> Brian ONeill > >> Lead Architect, Health Market Science (http://healthmarketscience.com) > >> mobile:215.588.6024 > >> blog: http://weblogs.java.net/blog/boneill42/ > >> blog: http://brianoneill.blogspot.com/ > > > > > > > >-- > >Jonathan Ellis > >Project Chair, Apache Cassandra > >co-founder of DataStax, the source for professional Cassandra support > >http://www.datastax.com > > > -- Brian ONeill Lead Architect, Health Market Science (http://healthmarketscience.com) mobile:215.588.6024 blog: http://weblogs.java.net/blog/boneill42/ blog: http://brianoneill.blogspot.com/
