You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2009/08/06 04:43:14 UTC
[jira] Created: (CASSANDRA-347) disabling commitlog as alternative
to binarymemtable?
disabling commitlog as alternative to binarymemtable?
-----------------------------------------------------
Key: CASSANDRA-347
URL: https://issues.apache.org/jira/browse/CASSANDRA-347
Project: Cassandra
Issue Type: New Feature
Reporter: Jonathan Ellis
Assignee: Jonathan Ellis
IMO it's worth seeing if we can do without BMt since it's a secondary code path that doesn't see much use. so you'll get done with BMT, then nobody will really test it until the next big import job at which point little bugs will have crept in because it just doesn't get run much.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CASSANDRA-347) disabling commitlog as alternative
to binarymemtable?
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-347.
--------------------------------------
Resolution: Won't Fix
Assignee: (was: Jonathan Ellis)
Serialization really is a bottleneck... I'm afraid binarymemtable isn't going anywhere :)
> disabling commitlog as alternative to binarymemtable?
> -----------------------------------------------------
>
> Key: CASSANDRA-347
> URL: https://issues.apache.org/jira/browse/CASSANDRA-347
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jonathan Ellis
> Attachments: 347.patch
>
>
> IMO it's worth seeing if we can do without BMt since it's a secondary code path that doesn't see much use. so you'll get done with BMT, then nobody will really test it until the next big import job at which point little bugs will have crept in because it just doesn't get run much.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-347) disabling commitlog as alternative
to binarymemtable?
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-347:
-------------------------------------
Attachment: 347.patch
proof of concept patch. does not address things like system CFs that don't grow large enough to flush to disk on their own.
> disabling commitlog as alternative to binarymemtable?
> -----------------------------------------------------
>
> Key: CASSANDRA-347
> URL: https://issues.apache.org/jira/browse/CASSANDRA-347
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Attachments: 347.patch
>
>
> IMO it's worth seeing if we can do without BMt since it's a secondary code path that doesn't see much use. so you'll get done with BMT, then nobody will really test it until the next big import job at which point little bugs will have crept in because it just doesn't get run much.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-347) disabling commitlog as alternative
to binarymemtable?
Posted by "Michael Greene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Greene updated CASSANDRA-347:
-------------------------------------
Component/s: Core
> disabling commitlog as alternative to binarymemtable?
> -----------------------------------------------------
>
> Key: CASSANDRA-347
> URL: https://issues.apache.org/jira/browse/CASSANDRA-347
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Attachments: 347.patch
>
>
> IMO it's worth seeing if we can do without BMt since it's a secondary code path that doesn't see much use. so you'll get done with BMT, then nobody will really test it until the next big import job at which point little bugs will have crept in because it just doesn't get run much.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.