[jira] [Created] (CASSANDRA-4175) Reduce memory (and disk) space requirements with a column name/id map
Reduce memory (and disk) space requirements with a column name/id map - Key: CASSANDRA-4175 URL: https://issues.apache.org/jira/browse/CASSANDRA-4175 Project: Cassandra Issue Type: Improvement Reporter: Jonathan Ellis Fix For: 1.2 We spend a lot of memory on column names, both transiently (during reads) and more permanently (in the row cache). Compression mitigates this on disk but not on the heap. The overhead is significant for typical small column values, e.g., ints. Even though we intern once we get to the memtable, this affects writes too via very high allocation rates in the young generation, hence more GC activity. Now that CQL3 provides us some guarantees that column names must be defined before they are inserted, we could create a map of (say) 32-bit int column id, to names, and use that internally right up until we return a resultset to the client. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-4157) Allow KS + CF names up to 48 characters
Allow KS + CF names up to 48 characters --- Key: CASSANDRA-4157 URL: https://issues.apache.org/jira/browse/CASSANDRA-4157 Project: Cassandra Issue Type: Improvement Components: Core Affects Versions: 1.1.0 Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 1.1.0 CASSANDRA-2749 imposed a 32-character limit on KS and CF names. We can be a little more lenient than that and still be safe for path names (see CASSANDRA-4110). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-4148) Explore commitlog compression
Explore commitlog compression - Key: CASSANDRA-4148 URL: https://issues.apache.org/jira/browse/CASSANDRA-4148 Project: Cassandra Issue Type: New Feature Components: Core Reporter: Jonathan Ellis Priority: Minor Probably worth trading cpu for i/o, even sequential i/o. The wrinkle is that we probably can only compress our sync window at a time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-4136) get_paged_slices doesn't reset startColumn after first row
get_paged_slices doesn't reset startColumn after first row -- Key: CASSANDRA-4136 URL: https://issues.apache.org/jira/browse/CASSANDRA-4136 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 1.1.0 Reporter: Jonathan Ellis Assignee: Sylvain Lebresne Priority: Critical Fix For: 1.1.0 As an example, consider the WordCount example (see CASSANDRA-3883). WordCountSetup inserts 1000 rows, each with three columns: text3, text4, int1. (Some other miscellaneous columns are inserted in a few rows, but we can ignore them here.) Paging through with get_paged_slice calls with a count of 99, CFRecordReader will first retrieve 33 rows, the last of which we will call K. Then it will attempt to fetch 99 more columns, starting with row K column text4. The bug is that it will only fetch text4 for *each* subsequent row K+i, instead of returning (K, text4), (K+1, int1), (K+1, int3), (K+1, text4), etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-4130) update snitch documentation
update snitch documentation --- Key: CASSANDRA-4130 URL: https://issues.apache.org/jira/browse/CASSANDRA-4130 Project: Cassandra Issue Type: Improvement Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 1.0.10 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-4110) Relax path length requirement for non-Windows platforms
Relax path length requirement for non-Windows platforms --- Key: CASSANDRA-4110 URL: https://issues.apache.org/jira/browse/CASSANDRA-4110 Project: Cassandra Issue Type: Improvement Affects Versions: 1.1.0 Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 1.1.0 As described at the bottom of CASSANDRA-2749, we only need to worry about total path length on Windows. For other platforms we only need to check the filename length. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-4088) Respect 1.0 cache settings as much as possible when upgrading
Respect 1.0 cache settings as much as possible when upgrading - Key: CASSANDRA-4088 URL: https://issues.apache.org/jira/browse/CASSANDRA-4088 Project: Cassandra Issue Type: Improvement Affects Versions: 1.1.0 Reporter: Jonathan Ellis Assignee: Pavel Yaskevich Fix For: 1.1.0 When converting a 1.0 schema to 1.1, we should look at the key and row caches (just whether they are en- or dis-abled) and set the caching setting accordingly. I think right now upgrading means all your row caching is gone until you update it manually. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-4087) Improve out-of-the-box cache settings
Improve out-of-the-box cache settings - Key: CASSANDRA-4087 URL: https://issues.apache.org/jira/browse/CASSANDRA-4087 Project: Cassandra Issue Type: Improvement Affects Versions: 1.1.0 Reporter: Jonathan Ellis Assignee: Pavel Yaskevich Fix For: 1.1.0 The default key cache of 2MB is significantly smaller than <= 1.0 (200 rows per CF) and much smaller than most production uses. How about min(5% of the heap, 100MB)? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-4080) Cut down on the comparisons needed during shouldPurge and needDeserialize
Cut down on the comparisons needed during shouldPurge and needDeserialize - Key: CASSANDRA-4080 URL: https://issues.apache.org/jira/browse/CASSANDRA-4080 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 1.1.1 shouldPurge in particular is still a performance sore point with LCS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-4072) Clean up DataOutputBuffer
Clean up DataOutputBuffer - Key: CASSANDRA-4072 URL: https://issues.apache.org/jira/browse/CASSANDRA-4072 Project: Cassandra Issue Type: Improvement Reporter: Jonathan Ellis The DataOutputBuffer/OutputBuffer split is unnecessarily baroque. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-4067) Report lifetime compaction throughput
Report lifetime compaction throughput - Key: CASSANDRA-4067 URL: https://issues.apache.org/jira/browse/CASSANDRA-4067 Project: Cassandra Issue Type: Improvement Components: Tools Reporter: Jonathan Ellis Assignee: Brandon Williams Priority: Trivial Fix For: 1.1.0 Would be useful to be able to monitor total compaction throughput without having to poll frequently enough to make sure we get every CompactionInfo object. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-4040) Add key_alias, key_validation_class to obsolete keywords in cql3
Add key_alias, key_validation_class to obsolete keywords in cql3 Key: CASSANDRA-4040 URL: https://issues.apache.org/jira/browse/CASSANDRA-4040 Project: Cassandra Issue Type: Bug Components: API Affects Versions: 1.1.0 Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 1.1.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-4039) CQL3 ALTER should deal with columns, not old thrift metadata
CQL3 ALTER should deal with columns, not old thrift metadata Key: CASSANDRA-4039 URL: https://issues.apache.org/jira/browse/CASSANDRA-4039 Project: Cassandra Issue Type: Bug Components: API Affects Versions: 1.1.0 Reporter: Jonathan Ellis Assignee: paul cannon Fix For: 1.1.0 key alias, default validator, column metadata should not be modified as such; rather, we should alter by column name. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-4018) Add column metadata to system columnfamilies
Add column metadata to system columnfamilies Key: CASSANDRA-4018 URL: https://issues.apache.org/jira/browse/CASSANDRA-4018 Project: Cassandra Issue Type: Improvement Reporter: Jonathan Ellis Priority: Minor Fix For: 1.1.1 CASSANDRA-3792 adds this to the schema CFs; we should modernize the other system CFs as well -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-4017) Unify migrations
Unify migrations Key: CASSANDRA-4017 URL: https://issues.apache.org/jira/browse/CASSANDRA-4017 Project: Cassandra Issue Type: Improvement Components: Core Affects Versions: 1.1.0 Reporter: Jonathan Ellis Fix For: 1.1.0 Now that we can send a schema as a RowMutation, there's no need to keep separate add/drop/update migration classes around. Let's just send the schema to our counterparts and let them figure out what changed. Currently we have "figure out what changed" code to both generate migrations on the sender, and for application on the target, which adds complexity. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-4012) Load-from-flat-file data import tool
Load-from-flat-file data import tool Key: CASSANDRA-4012 URL: https://issues.apache.org/jira/browse/CASSANDRA-4012 Project: Cassandra Issue Type: New Feature Components: Tools Reporter: Jonathan Ellis Assignee: paul cannon Fix For: 1.1.1 Would like to be able to import data from a comma-delimited or tab-delimited file, one "row" per line. (That is, "row" can be "logical row" as in http://www.datastax.com/dev/blog/schema-in-cassandra-1-1.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3974) Per-CF TTL
Per-CF TTL
--
Key: CASSANDRA-3974
URL: https://issues.apache.org/jira/browse/CASSANDRA-3974
Project: Cassandra
Issue Type: New Feature
Reporter: Jonathan Ellis
Priority: Minor
Per-CF TTL would allow compaction optimizations ("drop an entire sstable's
worth of expired data") that we can't do with per-column.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3970) JVM crash in streamingTransferTest on Windows
JVM crash in streamingTransferTest on Windows
-
Key: CASSANDRA-3970
URL: https://issues.apache.org/jira/browse/CASSANDRA-3970
Project: Cassandra
Issue Type: Bug
Components: Tests
Reporter: Jonathan Ellis
Fix For: 1.1.0
{noformat}
$ ant test -Dtest.name=StreamingTransferTest
...
[junit] Testsuite: org.apache.cassandra.streaming.StreamingTransferTest
[junit] #
[junit] # A fatal error has been detected by the Java Runtime Environment:
[junit] #
[junit] # EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x6da5ccca,
pid=95744, tid=94924
[junit] #
[junit] # JRE version: 6.0_27-b07
[junit] # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.2-b06 mixed mode
windows-amd64 compressed oops)
[junit] # Problematic frame:
[junit] # V [jvm.dll+0x1a]
[junit] #
[junit] # An error report file with more information is saved as:
[junit] # c:\Users\Jonathan\projects\cassandra\git\hs_err_pid95744.log
[junit] #
[junit] # If you would like to submit a bug report, please visit:
[junit] # http://java.sun.com/webapps/bugreport/crash.jsp
[junit] #
[junit] Testsuite: org.apache.cassandra.streaming.StreamingTransferTest
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
[junit]
[junit] Testcase:
org.apache.cassandra.streaming.StreamingTransferTest:testTransferTable:
Caused an ERROR
[junit] Forked Java VM exited abnormally. Please note the time in the report
does not reflect the time until the VM exit.
[junit] junit.framework.AssertionFailedError: Forked Java VM exited abnormally.
Please note the time in the report does not reflect the time until the VM exit.
[junit]
[junit]
[junit] Test org.apache.cassandra.streaming.StreamingTransferTest FAILED
(crashed)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3968) LoadNewSSTables can conflict with old incremental backups
LoadNewSSTables can conflict with old incremental backups - Key: CASSANDRA-3968 URL: https://issues.apache.org/jira/browse/CASSANDRA-3968 Project: Cassandra Issue Type: Bug Reporter: Jonathan Ellis Priority: Minor Fix For: 1.1.0 If we load a new sstable from the filesystem with a generation in our "past", the incremental backup hard link may conflict with an existing one. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3967) Test fixes for Windows
Test fixes for Windows -- Key: CASSANDRA-3967 URL: https://issues.apache.org/jira/browse/CASSANDRA-3967 Project: Cassandra Issue Type: Bug Components: Tests Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 1.1.0 - SchemaLoader initializes CommitLog, creating empty segments; CleanupHelper then errors out trying to delete them (because they are still open) - CFS.clearUnsafe resets the sstable generation but does not remove the sstables involved, so Windows will error out trying to rename over the existing ones -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3958) Remove random HH delay
Remove random HH delay
--
Key: CASSANDRA-3958
URL: https://issues.apache.org/jira/browse/CASSANDRA-3958
Project: Cassandra
Issue Type: Improvement
Components: Core
Reporter: Jonathan Ellis
Assignee: Jonathan Ellis
Priority: Trivial
Fix For: 1.1.0
{code}
. // sleep a random amount to stagger handoff delivery from different
replicas.
// (if we had to wait, then gossiper randomness took care of that for
us already.)
if (waited == 0)
{
// use a 'rounded' sleep interval because of a strange bug with
windows: CASSANDRA-3375
int sleep = FBUtilities.threadLocalRandom().nextInt(2000) * 30;
logger_.debug("Sleeping {}ms to stagger hint delivery", sleep);
Thread.sleep(sleep);
}
{code}
This is obsolete now that we have the per-hint configurable delay. And large
hint loads (which are the ones that matter most) are going to overlap anyway
even with the maximum 60s difference.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3957) Supercolumn serialization assertion failure
Supercolumn serialization assertion failure
---
Key: CASSANDRA-3957
URL: https://issues.apache.org/jira/browse/CASSANDRA-3957
Project: Cassandra
Issue Type: Bug
Reporter: Jonathan Ellis
Assignee: Yuki Morishita
Fix For: 1.0.9
As reported at
http://mail-archives.apache.org/mod_mbox/cassandra-user/201202.mbox/%3CCADJL=w5kH5TEQXOwhTn5Jm3cmR4Rj=nfjcqlryxv7plyasi...@mail.gmail.com%3E,
{noformat}
ERROR 10:51:44,282 Fatal exception in thread
Thread[COMMIT-LOG-WRITER,5,main]
java.lang.AssertionError: Final buffer length 4690 to accomodate data size
of 2347 (predicted 2344) for RowMutation(keyspace='Player',
key='36336138643338652d366162302d343334392d383466302d356166643863353133356465',
modifications=[ColumnFamily(PlayerCity [SuperColumn(owneditem_1019
[]),SuperColumn(owneditem_1024 []),SuperColumn(owneditem_1026
[]),SuperColumn(owneditem_1074 []),SuperColumn(owneditem_1077
[]),SuperColumn(owneditem_1084 []),SuperColumn(owneditem_1094
[]),SuperColumn(owneditem_1130 []),SuperColumn(owneditem_1136
[]),SuperColumn(owneditem_1141 []),SuperColumn(owneditem_1142
[]),SuperColumn(owneditem_1145 []),SuperColumn(owneditem_1218
[636f6e6e6563746564:false:5@1329648704269002
,63757272656e744865616c7468:false:3@1329648704269006
,656e64436f6e737472756374696f6e54696d65:false:13@1329648704269007
,6964:false:4@1329648704269000,6974656d4964:false:15@1329648704269001
,6c61737444657374726f79656454696d65:false:1@1329648704269008
,6c61737454696d65436f6c6c6563746564:false:13@1329648704269005
,736b696e4964:false:7@1329648704269009,78:false:4@1329648704269003
,79:false:3@1329648704269004,]),SuperColumn(owneditem_133
[]),SuperColumn(owneditem_134 []),SuperColumn(owneditem_135
[]),SuperColumn(owneditem_141 []),SuperColumn(owneditem_147
[]),SuperColumn(owneditem_154 []),SuperColumn(owneditem_159
[]),SuperColumn(owneditem_171 []),SuperColumn(owneditem_253
[]),SuperColumn(owneditem_422 []),SuperColumn(owneditem_438
[]),SuperColumn(owneditem_515 []),SuperColumn(owneditem_521
[]),SuperColumn(owneditem_523 []),SuperColumn(owneditem_525
[]),SuperColumn(owneditem_562 []),SuperColumn(owneditem_61
[]),SuperColumn(owneditem_634 []),SuperColumn(owneditem_636
[]),SuperColumn(owneditem_71 []),SuperColumn(owneditem_712
[]),SuperColumn(owneditem_720 []),SuperColumn(owneditem_728
[]),SuperColumn(owneditem_787 []),SuperColumn(owneditem_797
[]),SuperColumn(owneditem_798 []),SuperColumn(owneditem_838
[]),SuperColumn(owneditem_842 []),SuperColumn(owneditem_847
[]),SuperColumn(owneditem_849 []),SuperColumn(owneditem_851
[]),SuperColumn(owneditem_852 []),SuperColumn(owneditem_853
[]),SuperColumn(owneditem_854 []),SuperColumn(owneditem_857
[]),SuperColumn(owneditem_858 []),SuperColumn(owneditem_874
[]),SuperColumn(owneditem_884 []),SuperColumn(owneditem_886
[]),SuperColumn(owneditem_908 []),SuperColumn(owneditem_91
[]),SuperColumn(owneditem_911 []),SuperColumn(owneditem_930
[]),SuperColumn(owneditem_934 []),SuperColumn(owneditem_937
[]),SuperColumn(owneditem_944 []),SuperColumn(owneditem_945
[]),SuperColumn(owneditem_962 []),SuperColumn(owneditem_963
[]),SuperColumn(owneditem_964 []),])])
at
org.apache.cassandra.utils.FBUtilities.serialize(FBUtilities.java:682)
at
org.apache.cassandra.db.RowMutation.getSerializedBuffer(RowMutation.java:279)
at
org.apache.cassandra.db.commitlog.CommitLogSegment.write(CommitLogSegment.java:122)
at
org.apache.cassandra.db.commitlog.CommitLog$LogRecordAdder.run(CommitLog.java:599)
at
org.apache.cassandra.db.commitlog.PeriodicCommitLogExecutorService$1.runMayThrow(PeriodicCommitLogExecutorService.java:49)
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
at java.lang.Thread.run(Thread.java:662)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3952) avoid quadratic startup time in LeveledManifest
avoid quadratic startup time in LeveledManifest
---
Key: CASSANDRA-3952
URL: https://issues.apache.org/jira/browse/CASSANDRA-3952
Project: Cassandra
Issue Type: Improvement
Components: Core
Reporter: Jonathan Ellis
Assignee: Jonathan Ellis
Priority: Minor
Fix For: 1.1.0, 1.1.1
Checking that each sstable is in the manifest on startup is O(N**2) in the
number of sstables:
{code}
. // ensure all SSTables are in the manifest
for (SSTableReader ssTableReader : cfs.getSSTables())
{
if (manifest.levelOf(ssTableReader) < 0)
manifest.add(ssTableReader);
}
{code}
{code}
private int levelOf(SSTableReader sstable)
{
for (int level = 0; level < generations.length; level++)
{
if (generations[level].contains(sstable))
return level;
}
return -1;
}
{code}
Note that the contains call is a linear List.contains.
We need to switch to a sorted list and bsearch, or a tree, to support TB-levels
of data in LeveledCompactionStrategy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3929) Support row size limits
Support row size limits --- Key: CASSANDRA-3929 URL: https://issues.apache.org/jira/browse/CASSANDRA-3929 Project: Cassandra Issue Type: New Feature Components: Core Reporter: Jonathan Ellis We currently support expiring columns by time-to-live; we've also had requests for keeping the most recent N columns in a row. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3925) ORDER BY syntax
ORDER BY syntax
---
Key: CASSANDRA-3925
URL: https://issues.apache.org/jira/browse/CASSANDRA-3925
Project: Cassandra
Issue Type: Sub-task
Reporter: Jonathan Ellis
Assignee: Sylvain Lebresne
Priority: Minor
Fix For: 1.1.1
I think we should switch to standard {{ORDER BY x [DESC]}} syntax, for several
reasons.
First, because {{ORDER [DESC]}} is not very readable. By that I mean, you have
no idea what it means unless you cross reference with the CF definition.
Second, because it's not a sufficiently better fit than the SQL syntax to
justify inventing our own.
Third (and this is the big one) I strongly suspect that we're going to start
supporting at least limited run-time ordering in the near future, and this
gives us some future proofing while working reasonably well in the meantime: we
can simply reject with IRE {{ORDER BY}} requests that aren't compatible with
the comparator, similarly to what we used to do with unindexed WHERE
expressions. (Which is also a good example of us being dragged kicking and
screaming into being more flexible at query time...)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3921) Compaction doesn't clear out expired tombstones from SerializingCache
Compaction doesn't clear out expired tombstones from SerializingCache
-
Key: CASSANDRA-3921
URL: https://issues.apache.org/jira/browse/CASSANDRA-3921
Project: Cassandra
Issue Type: Bug
Affects Versions: 0.8.0
Reporter: Jonathan Ellis
Priority: Minor
Fix For: 1.1.0
Compaction calls removeDeletedInCache, which looks like this:
{code}
. public void removeDeletedInCache(DecoratedKey key)
{
ColumnFamily cachedRow = cfs.getRawCachedRow(key);
if (cachedRow != null)
ColumnFamilyStore.removeDeleted(cachedRow, gcBefore);
}
{code}
For the SerializingCache, this means it calls removeDeleted on a temporary,
deserialized copy, which leaves the cache contents unaffected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3919) Dropping a column should do more than just remove the definition
Dropping a column should do more than just remove the definition
Key: CASSANDRA-3919
URL: https://issues.apache.org/jira/browse/CASSANDRA-3919
Project: Cassandra
Issue Type: Sub-task
Components: Core
Reporter: Jonathan Ellis
Assignee: Sylvain Lebresne
Fix For: 1.1.1
Dropping a column should:
- immediately make it unavailable for {{SELECT}}, including {{SELECT *}}
- eventually (i.e., post-compaction) reclaim the space formerly used by that
column
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3885) Support multiple ranges in SliceQueryFilter
Support multiple ranges in SliceQueryFilter --- Key: CASSANDRA-3885 URL: https://issues.apache.org/jira/browse/CASSANDRA-3885 Project: Cassandra Issue Type: Sub-task Reporter: Jonathan Ellis -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3871) Turn compression on by default
Turn compression on by default -- Key: CASSANDRA-3871 URL: https://issues.apache.org/jira/browse/CASSANDRA-3871 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Jonathan Ellis Assignee: Jonathan Ellis Fix For: 1.1 Compression has been available but off by default since 1.0.0. It's enabled in a lot of production environments now, with no major problems found. (Some problems with customizing the block size were found and fixed in the 1.0 releases.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3816) Improve visibility of Cassandra packages
Improve visibility of Cassandra packages Key: CASSANDRA-3816 URL: https://issues.apache.org/jira/browse/CASSANDRA-3816 Project: Cassandra Issue Type: Improvement Components: Documentation & website Reporter: Jonathan Ellis Assignee: Jonathan Ellis The preferred way to install (and upgrade) Cassandra is through Debian and RPM packages, but the current "Take Action" download box on the front page only links the binary tarball. Even clicking through to "other options" (http://cassandra.apache.org/download/) doesn't mention anything but tarballs for the core server. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3803) snapshot-before-compaction snapshots entire keyspace
snapshot-before-compaction snapshots entire keyspace Key: CASSANDRA-3803 URL: https://issues.apache.org/jira/browse/CASSANDRA-3803 Project: Cassandra Issue Type: Bug Components: Core Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 1.1 Should only snapshot the CF being compacted -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3793) remove deprecated KsDef.replication_factor field
remove deprecated KsDef.replication_factor field Key: CASSANDRA-3793 URL: https://issues.apache.org/jira/browse/CASSANDRA-3793 Project: Cassandra Issue Type: Improvement Components: API Affects Versions: 0.8.0 Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 1.1 KsDef.replication_factor is superceded by KsDef.strategy_options, but we've been keeping special-case code around to populate the old r_f field for SimpleStrategy so that pre-0.8 clients can still create and introspect the schema. Time to clean that up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3792) add type information to new schema_ columnfamilies
add type information to new schema_ columnfamilies -- Key: CASSANDRA-3792 URL: https://issues.apache.org/jira/browse/CASSANDRA-3792 Project: Cassandra Issue Type: Improvement Components: Core Affects Versions: 1.1 Reporter: Jonathan Ellis Assignee: Jonathan Ellis Fix For: 1.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3772) Evaluate Murmur3-based partitioner
Evaluate Murmur3-based partitioner -- Key: CASSANDRA-3772 URL: https://issues.apache.org/jira/browse/CASSANDRA-3772 Project: Cassandra Issue Type: New Feature Reporter: Jonathan Ellis Fix For: 1.2 MD5 is a relatively heavyweight hash to use when we don't need cryptographic qualities, just a good output distribution. Let's see how much overhead we can save by using Murmur3 instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3771) Allow paging through non-ordered partitioner results in CQL3
Allow paging through non-ordered partitioner results in CQL3 Key: CASSANDRA-3771 URL: https://issues.apache.org/jira/browse/CASSANDRA-3771 Project: Cassandra Issue Type: New Feature Components: API Affects Versions: 1.1 Reporter: Jonathan Ellis Fix For: 1.1 CQL < 3 silently turns a "key >= X" into "token(key) >= token(X)". This is not what users will expect, since many of the rows returned will not in fact satisfy the requested key inequality. We should add syntax that makes the difference between keys and tokens explicit, possibly with a token() "function" as imagined here. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3765) hadoop word count example is unable to output to cassandra with default settings
hadoop word count example is unable to output to cassandra with default settings
Key: CASSANDRA-3765
URL: https://issues.apache.org/jira/browse/CASSANDRA-3765
Project: Cassandra
Issue Type: Bug
Components: Contrib
Reporter: Jonathan Ellis
Assignee: Brandon Williams
Priority: Minor
Fix For: 1.0.8
{noformat}
12/01/21 06:03:16 WARN mapred.LocalJobRunner: job_local_0001
java.lang.NullPointerException
at
org.apache.cassandra.utils.FBUtilities.newPartitioner(FBUtilities.java:407)
at
org.apache.cassandra.hadoop.ConfigHelper.getOutputPartitioner(ConfigHelper.java:384)
at org.apache.cassandra.client.RingCache.(RingCache.java:58)
at
org.apache.cassandra.hadoop.ColumnFamilyRecordWriter.(ColumnFamilyRecordWriter.java:99)
at
org.apache.cassandra.hadoop.ColumnFamilyRecordWriter.(ColumnFamilyRecordWriter.java:93)
at
org.apache.cassandra.hadoop.ColumnFamilyOutputFormat.getRecordWriter(ColumnFamilyOutputFormat.java:132)
at
org.apache.cassandra.hadoop.ColumnFamilyOutputFormat.getRecordWriter(ColumnFamilyOutputFormat.java:62)
at
org.apache.hadoop.mapred.ReduceTask.runNewReducer(ReduceTask.java:553)
at org.apache.hadoop.mapred.ReduceTask.run(ReduceTask.java:408)
{noformat}
(Output to filesystem still works.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3764) cqlsh doesn't error out immediately for use of invalid keyspace
cqlsh doesn't error out immediately for use of invalid keyspace
---
Key: CASSANDRA-3764
URL: https://issues.apache.org/jira/browse/CASSANDRA-3764
Project: Cassandra
Issue Type: Bug
Components: Tools
Reporter: Jonathan Ellis
Assignee: paul cannon
Priority: Minor
Fix For: 1.0.8
{noformat}
cqlsh> use wordcoun;
cqlsh:wordcoun> select * from input_words;
Bad Request: Keyspace wordcoun does not exist
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3753) Update CqlPreparedResult to provide type information
Update CqlPreparedResult to provide type information Key: CASSANDRA-3753 URL: https://issues.apache.org/jira/browse/CASSANDRA-3753 Project: Cassandra Issue Type: Improvement Components: API Affects Versions: 1.1 Reporter: Jonathan Ellis Priority: Critical Fix For: 1.1 As discussed on CASSANDRA-3634, adding type information to a prepared statement would allow more client-side error checking. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3735) Fix "Unable to create hard link" SSTableReaderTest error messages
Fix "Unable to create hard link" SSTableReaderTest error messages
-
Key: CASSANDRA-3735
URL: https://issues.apache.org/jira/browse/CASSANDRA-3735
Project: Cassandra
Issue Type: Bug
Reporter: Jonathan Ellis
Priority: Minor
Sample failure (on Windows):
{noformat}
[junit] java.io.IOException: Exception while executing the command: cmd /c
mklink /H
C:\Users\Jonathan\projects\cassandra\git\build\test\cassandra\data\Keyspace1\backups\Standard1-hc-1-Index.db
c:\Users\Jonathan\projects\cassandra\git\build\test\cassandra\data\Keyspace1\Standard1-hc-1-Index.db,command
error Code: 1, command output: Cannot create a file when that file already
exists.
[junit]
[junit] at org.apache.cassandra.utils.CLibrary.exec(CLibrary.java:213)
[junit] at
org.apache.cassandra.utils.CLibrary.createHardLinkWithExec(CLibrary.java:188)
[junit] at
org.apache.cassandra.utils.CLibrary.createHardLink(CLibrary.java:151)
[junit] at
org.apache.cassandra.io.sstable.SSTableReader.createLinks(SSTableReader.java:833)
[junit] at
org.apache.cassandra.db.DataTracker$1.runMayThrow(DataTracker.java:161)
[junit] at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
[junit] at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
[junit] at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
[junit] at java.util.concurrent.FutureTask.run(FutureTask.java:138)
[junit] at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
[junit] at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)
[junit] at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[junit] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[junit] at java.lang.Thread.run(Thread.java:662)
[junit] ERROR 17:10:17,111 Fatal exception in thread
Thread[NonPeriodicTasks:1,5,main]
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3734) Support native link w/o JNA in Java7
Support native link w/o JNA in Java7 Key: CASSANDRA-3734 URL: https://issues.apache.org/jira/browse/CASSANDRA-3734 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Jonathan Ellis Priority: Minor Fix For: 1.2 Java7 provides native support for hard links: http://docs.oracle.com/javase/7/docs/api/java/nio/file/Files.html#createLink(java.nio.file.Path, java.nio.file.Path) We should prefer this method when Java7 is the host. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3716) Clean up isMarkedForDelete / getLocalDeletionTime
Clean up isMarkedForDelete / getLocalDeletionTime - Key: CASSANDRA-3716 URL: https://issues.apache.org/jira/browse/CASSANDRA-3716 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Jonathan Ellis Assignee: Sylvain Lebresne Fix For: 1.1 As explained in CASSANDRA-3579, isMarkedForDelete() depends on the current system clock so it can change during a two-pass compaction. Suggested fix is to replace iMFD + gLDT with a getExpirationTime method, so comparison with the compaction's gcBefore will remain constant. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3709) Add a token generator to standard tools
Add a token generator to standard tools --- Key: CASSANDRA-3709 URL: https://issues.apache.org/jira/browse/CASSANDRA-3709 Project: Cassandra Issue Type: New Feature Components: Tools Reporter: Jonathan Ellis Assignee: paul cannon Priority: Minor Fix For: 1.1 We recommend spacing nodes in a new cluster evenly around the ring; we should provide a tool to generate appropriate tokens for a cluster of size X. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3708) Support "composite prefix" tombstones
Support "composite prefix" tombstones - Key: CASSANDRA-3708 URL: https://issues.apache.org/jira/browse/CASSANDRA-3708 Project: Cassandra Issue Type: Sub-task Reporter: Jonathan Ellis -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3707) Add KeyspaceChange CqlResultType
Add KeyspaceChange CqlResultType Key: CASSANDRA-3707 URL: https://issues.apache.org/jira/browse/CASSANDRA-3707 Project: Cassandra Issue Type: New Feature Components: API Reporter: Jonathan Ellis Priority: Minor Fix For: 1.1 High level clients want to handle failover and load balancing transparently to the application, which means not just connection pooling but moving an existing connection to another server if necessary. When this happens, the client needs to know what the active keyspace was before failover, so it can set it to the same one in the new connection. Currently some clients handle this by checking for "SET KEYSPACE" queries, which violates the design principle that clients shouldn't have to parse CQL. Adding a new CqlResultType (that is set in response to a SET KEYSPACE command) would make this unnecessary. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3706) Back up configuration files on startup
Back up configuration files on startup -- Key: CASSANDRA-3706 URL: https://issues.apache.org/jira/browse/CASSANDRA-3706 Project: Cassandra Issue Type: New Feature Components: Tools Reporter: Jonathan Ellis Priority: Minor Snapshot can backup user data, but it's also nice to be able to have known-good configurations saved as well in case of accidental snafus or even catastrophic loss of a cluster. If we check for changes to cassandra.yaml, cassandra-env.sh, and maybe log4j-server.properties on startup, we can back them up to a columnfamily that can then be handled by normal snapshot/backup procedures. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3700) SelectStatement start/end key are not set correctly when a key alias is involved
SelectStatement start/end key are not set correctly when a key alias is involved Key: CASSANDRA-3700 URL: https://issues.apache.org/jira/browse/CASSANDRA-3700 Project: Cassandra Issue Type: Bug Reporter: Jonathan Ellis Assignee: Pavel Yaskevich start/end key are set by antlr in WhereClause, but this depends on the "KEY" keyword. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3687) Local range scans are not run on the read stage
Local range scans are not run on the read stage --- Key: CASSANDRA-3687 URL: https://issues.apache.org/jira/browse/CASSANDRA-3687 Project: Cassandra Issue Type: Bug Reporter: Jonathan Ellis Priority: Minor Fix For: 1.2 Running directly on the client request/StorageProxy thread means we're now allowing one range scan per thrift thread instead of one per read stage thread [which may be more, or less, depending on thrift server mode], and it bypasses the "drop hopeless requests" overcapacity protection built in there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3685) CQL support for non-utf8 column names
CQL support for non-utf8 column names
-
Key: CASSANDRA-3685
URL: https://issues.apache.org/jira/browse/CASSANDRA-3685
Project: Cassandra
Issue Type: New Feature
Components: API
Reporter: Jonathan Ellis
Fix For: 1.2
Eric Evans' suggestions from the mailing list:
{code}
CREATE TABLE test (
int(10) text,
uuid(92d21d0a-d6cb-437c-9d3f-b67aa733a19f) bigint
)
{code}
{code}
CREATE TABLE test (
(int)10 text,
(uuid)92d21d0a-d6cb-437c-9d3f-b67aa733a19f bigint
)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3681) Multiple threads can attempt hint handoff to the same target
Multiple threads can attempt hint handoff to the same target Key: CASSANDRA-3681 URL: https://issues.apache.org/jira/browse/CASSANDRA-3681 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 1.0.0 Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 1.0.7 HintedHandOffManager attempts to prevent multiple threads sending hints to the same target with the queuedDeliveries set, but the code is buggy. If two handoffs *do* occur concurrently, the second thread can use an arbitrarily large amount of memory skipping tombstones when it starts paging from the beginning of the hint row, looking for the first live hint. (This is not a problem with a single thread, since it always pages starting with the last-seen hint column name, effectively skipping the tombstones. Then it compacts when it's done.) Technically this bug is present in all older Cassandra releases, but it only causes problems in 1.0.x since the hint rows tend to be much larger (since there is one hint per write containing the entire mutation, instead of just one per row consisting of just the key). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3679) clean up multithreaded streaming to use a ConcurrentMap instead of explicit locking
clean up multithreaded streaming to use a ConcurrentMap instead of explicit locking --- Key: CASSANDRA-3679 URL: https://issues.apache.org/jira/browse/CASSANDRA-3679 Project: Cassandra Issue Type: Improvement Affects Versions: 1.1 Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 1.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3661) Re-introduce timeout debug messages in CassandraServer
Re-introduce timeout debug messages in CassandraServer
--
Key: CASSANDRA-3661
URL: https://issues.apache.org/jira/browse/CASSANDRA-3661
Project: Cassandra
Issue Type: Improvement
Components: API
Affects Versions: 0.8.0
Reporter: Jonathan Ellis
Assignee: Brandon Williams
Priority: Trivial
Fix For: 0.8.10, 1.0.7
In 0.7 we log at debug when returning TOE back to the client:
{code}
. catch (TimeoutException e)
{
logger.debug("... timed out");
throw new TimedOutException();
}
{code}
This is primarily useful when reading through debug logs to make it obvious
when StorageProxy gave up waiting and cleared its callbacks.
At some point this got removed from 0.8+. (Or possibly never got correctly
merged upwards.) Let's fix this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3657) Allow extending CompositeType comparator
Allow extending CompositeType comparator Key: CASSANDRA-3657 URL: https://issues.apache.org/jira/browse/CASSANDRA-3657 Project: Cassandra Issue Type: New Feature Components: API, Core Reporter: Jonathan Ellis Assignee: Jonathan Ellis Fix For: 1.1 Quoting Sylvain from CASSANDRA-2474, bq. if you declare a comparator like CompositeType(IntType, UUIDType, UTF8Type), you can have columns that have only some prefix of the component (typically '42:92d21d0a-d6cb-437c-9d3f-b67aa733a19f' is a valid column name for that comparator), and as a consequence it would be possible to allow 'extend' the preceding comparator to say CompositeType(IntType, UUIDType, UTF8Type, IntType) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3656) GC can take 0 ms
GC can take 0 ms Key: CASSANDRA-3656 URL: https://issues.apache.org/jira/browse/CASSANDRA-3656 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 0.8.7, 0.7.9 Reporter: Jonathan Ellis Priority: Trivial Fix For: 0.8.10, 1.0.7 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3648) Repair should validate checksums before streaming
Repair should validate checksums before streaming - Key: CASSANDRA-3648 URL: https://issues.apache.org/jira/browse/CASSANDRA-3648 Project: Cassandra Issue Type: New Feature Reporter: Jonathan Ellis Priority: Minor Fix For: 1.2 We have block checksums and sha1 full-file hashes, but currently we do not validate these before streaming in a repair. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3647) Support arbitrarily nested "documents"
Support arbitrarily nested "documents" -- Key: CASSANDRA-3647 URL: https://issues.apache.org/jira/browse/CASSANDRA-3647 Project: Cassandra Issue Type: New Feature Components: API, Core Reporter: Jonathan Ellis Composite columns introduce the ability to have arbitrarily nested data in a Cassandra row. We should expose this through CQL. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3622) clean up openbitset
clean up openbitset --- Key: CASSANDRA-3622 URL: https://issues.apache.org/jira/browse/CASSANDRA-3622 Project: Cassandra Issue Type: Task Components: Core Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 1.1 Our OpenBitSet no longer supports expanding the set post-construction. Should update documentation to reflect that. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3617) Clean up and optimize Message
Clean up and optimize Message - Key: CASSANDRA-3617 URL: https://issues.apache.org/jira/browse/CASSANDRA-3617 Project: Cassandra Issue Type: Improvement Reporter: Jonathan Ellis The Message class has grown largely by accretion and it shows. There are several problems: - Outbound and inbound messages aren't really the same thing and should not be conflated - We pre-serialize message bodies to byte[], then copy those bytes onto the Socket buffer, instead of just keeping a reference to the object being serialized and then writing it out directly to the socket - MessagingService versioning is poorly encapsulating, scattering version variables and references to things like CachingMessageProducer across the codebase -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3584) Check for 0.0.0.0 is incorrect
Check for 0.0.0.0 is incorrect -- Key: CASSANDRA-3584 URL: https://issues.apache.org/jira/browse/CASSANDRA-3584 Project: Cassandra Issue Type: Bug Components: Hadoop Affects Versions: 1.0.1 Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 1.0.6 As noted by Jake in the comments to CASSANDRA-3214, we are using == for a String comparison. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3583) Add "rebuild index" JMX command
Add "rebuild index" JMX command --- Key: CASSANDRA-3583 URL: https://issues.apache.org/jira/browse/CASSANDRA-3583 Project: Cassandra Issue Type: New Feature Components: Core, Tools Reporter: Jonathan Ellis Assignee: Vijay Priority: Minor Fix For: 1.1 CASSANDRA-1740 allows aborting an index build, but there is no way to re-attempt the build without restarting the server. We've also had requests to allow rebuilding an index that *has* been built, so it would be nice to kill two birds with one stone here. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3582) UserInterruptedException is poorly encapsulated
UserInterruptedException is poorly encapsulated --- Key: CASSANDRA-3582 URL: https://issues.apache.org/jira/browse/CASSANDRA-3582 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 1.1 Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 1.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3578) Multithreaded commitlog
Multithreaded commitlog --- Key: CASSANDRA-3578 URL: https://issues.apache.org/jira/browse/CASSANDRA-3578 Project: Cassandra Issue Type: Improvement Reporter: Jonathan Ellis Priority: Minor Brian Aker pointed out a while ago that allowing multiple threads to modify the commitlog simultaneously (reserving space for each with a CAS first, the way we do in the SlabAllocator.Region.allocate) can improve performance, since you're not bottlenecking on a single thread to do all the copying and CRC computation. Now that we use mmap'd CommitLog segments (CASSANDRA-3411) this becomes doable. (moved from CASSANDRA-622, which was getting a bit muddled.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3576) make AbstractSSTableSimpleWriters threadsafe
make AbstractSSTableSimpleWriters threadsafe Key: CASSANDRA-3576 URL: https://issues.apache.org/jira/browse/CASSANDRA-3576 Project: Cassandra Issue Type: New Feature Components: Core Affects Versions: 0.8.1 Reporter: Jonathan Ellis Assignee: Sylvain Lebresne Priority: Minor Fix For: 1.1 I took a quick look and the Unsorted writer has a non-threadsafe getColumnFamily method. I did not look deeper than that. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3567) remove unmaintained redhat packaging
remove unmaintained redhat packaging Key: CASSANDRA-3567 URL: https://issues.apache.org/jira/browse/CASSANDRA-3567 Project: Cassandra Issue Type: Task Components: Packaging Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 1.1 The redhat package hasn't been changed since it was updated for 0.7.0 over a year ago, and nobody noticed until Paul did for CASSANDRA-3458. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3566) Cache saving broken on windows
Cache saving broken on windows -- Key: CASSANDRA-3566 URL: https://issues.apache.org/jira/browse/CASSANDRA-3566 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 1.0.6 Reporter: Jonathan Ellis Assignee: Sylvain Lebresne Fix For: 1.0.6 CASSANDRA-1740 broke cache saving on Windows. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3565) CQL CF creation skips most of the validation code
CQL CF creation skips most of the validation code - Key: CASSANDRA-3565 URL: https://issues.apache.org/jira/browse/CASSANDRA-3565 Project: Cassandra Issue Type: Bug Components: API Affects Versions: 0.8.0 Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 1.0.6 Most validation is done by ThriftValidation.validateCfDef, which we call from QP when creating an index but not on CF creation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3564) flush before shutdown so restart is faster
flush before shutdown so restart is faster -- Key: CASSANDRA-3564 URL: https://issues.apache.org/jira/browse/CASSANDRA-3564 Project: Cassandra Issue Type: New Feature Components: Packaging Reporter: Jonathan Ellis Assignee: paul cannon Priority: Minor Fix For: 1.1 Cassandra handles flush in its shutdown hook for durable_writes=false CFs (otherwise we're *guaranteed* to lose data) but leaves it up to the operator otherwise. I'd rather leave it that way to offer these semantics: cassandra stop = shutdown nicely kill -INT = shutdown faster but don't lose any updates kill -KILL = lose most recent writes unless durable_writes=true and batch commits are on But if it's not reasonable to use nodetool from the init script then I guess we can just make the shutdown hook flush everything. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3554) Hints are not replayed unless node was marked down
Hints are not replayed unless node was marked down -- Key: CASSANDRA-3554 URL: https://issues.apache.org/jira/browse/CASSANDRA-3554 Project: Cassandra Issue Type: Bug Reporter: Jonathan Ellis If B drops a write from A because it is overwhelmed (but not dead), A will hint the write. But it will never get notified that B is back up (since it was never down), so it will never attempt hint delivery. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3541) Support timeuuid column names
Support timeuuid column names - Key: CASSANDRA-3541 URL: https://issues.apache.org/jira/browse/CASSANDRA-3541 Project: Cassandra Issue Type: New Feature Components: Tools Reporter: Jonathan Ellis Assignee: Pavel Yaskevich Priority: Minor Fix For: 1.0.5 Real-world Cassandra applications often use "wide rows" to denormalize queries into. Most often, this means they do a lot of appending to existing rows, with few overwrites. An easy way to add this to Stress would be to allow specifying timeuuid column names (which will be inherently sequential, or nearly so). For forwards-compatibility, we could add a --comparator option that only supports the existing Ascii type and the proposed UUID type, to start with. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3529) ConcurrentModificationException in Table.all()
ConcurrentModificationException in Table.all()
--
Key: CASSANDRA-3529
URL: https://issues.apache.org/jira/browse/CASSANDRA-3529
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 1.0.0
Reporter: Jonathan Ellis
Assignee: Jonathan Ellis
Priority: Trivial
Fix For: 1.0.4
{noformat}
[junit] java.util.ConcurrentModificationException
[junit] at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
[junit] at java.util.HashMap$KeyIterator.next(HashMap.java:828)
[junit] at
com.google.common.collect.Iterators$8.next(Iterators.java:750)
[junit] at
org.apache.cassandra.db.ColumnFamilyStore.all(ColumnFamilyStore.java:1509)
[junit] at
org.apache.cassandra.db.MeteredFlusher.countFlushingBytes(MeteredFlusher.java:118)
[junit] at
org.apache.cassandra.db.MeteredFlusher.run(MeteredFlusher.java:45)
[junit] at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
[junit] at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
[junit] at
java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
[junit] at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
[junit] at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
[junit] at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
[junit] at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[junit] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[junit] at java.lang.Thread.run(Thread.java:662)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3524) add support for composite CFs to CQL
add support for composite CFs to CQL Key: CASSANDRA-3524 URL: https://issues.apache.org/jira/browse/CASSANDRA-3524 Project: Cassandra Issue Type: New Feature Components: API Reporter: Jonathan Ellis Assignee: paul cannon Priority: Minor Fix For: 1.0.4 I believe we want this in CREATE ASSUME and ALTER. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3523) support ALTER of CF attributes in CQL
support ALTER of CF attributes in CQL - Key: CASSANDRA-3523 URL: https://issues.apache.org/jira/browse/CASSANDRA-3523 Project: Cassandra Issue Type: New Feature Components: API, Tools Reporter: Jonathan Ellis Assignee: paul cannon Priority: Minor Fix For: 1.0.4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3498) Add same-row contention mode to stress tool
Add same-row contention mode to stress tool --- Key: CASSANDRA-3498 URL: https://issues.apache.org/jira/browse/CASSANDRA-3498 Project: Cassandra Issue Type: New Feature Components: Tools Reporter: Jonathan Ellis Assignee: Pavel Yaskevich Priority: Minor Fix For: 1.1 For CASSANDRA-2893 and other scenarios we'd like to generate non-unique rows to insert. (Maybe we can re-use the same pseudorandom distribution code we already have for reads.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3479) add read from/write to file support to cqlsh
add read from/write to file support to cqlsh Key: CASSANDRA-3479 URL: https://issues.apache.org/jira/browse/CASSANDRA-3479 Project: Cassandra Issue Type: Improvement Reporter: Jonathan Ellis Assignee: paul cannon Priority: Minor Fix For: 1.0.3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3478) Add support for sstable forwards-compatibility
Add support for sstable forwards-compatibility -- Key: CASSANDRA-3478 URL: https://issues.apache.org/jira/browse/CASSANDRA-3478 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 1.0.3 Following on to CASSANDRA-3470. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3474) SSTableMetadata deserialization works but looks broken
SSTableMetadata deserialization works but looks broken
--
Key: CASSANDRA-3474
URL: https://issues.apache.org/jira/browse/CASSANDRA-3474
Project: Cassandra
Issue Type: Improvement
Components: Core
Affects Versions: 1.0.0
Reporter: Jonathan Ellis
Priority: Minor
Fix For: 1.0.3
This is confusing:
{code}
. if (!descriptor.usesHistogramAndReplayPositionStatsFile)
return deserialize(dis); // deserializes histogram
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3470) Add a second letter to Descriptor version
Add a second letter to Descriptor version - Key: CASSANDRA-3470 URL: https://issues.apache.org/jira/browse/CASSANDRA-3470 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Jonathan Ellis Assignee: Yuki Morishita Priority: Minor Fix For: 1.0.3 Versions g and h are actually forwards-compatible with version f, and more changes like that are easily forseeable (e.g., CASSANDRA-3407). It would be nice to have an extra version digit (h1, h2, ... ha, hb, ...). Otherwise our choices are forcing people to scrub for these changes (unacceptable) or not updating the Descriptor version, which is suboptimal since we don't know what the contents are until we try to read it and find the latest parts missing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3469) More fine-grained request statistics
More fine-grained request statistics
Key: CASSANDRA-3469
URL: https://issues.apache.org/jira/browse/CASSANDRA-3469
Project: Cassandra
Issue Type: New Feature
Components: Core
Reporter: Jonathan Ellis
Assignee: Yuki Morishita
Priority: Minor
Fix For: 1.1
It would be useful to split the CFS stats up by query type. slice vs named vs
range vs index, to start with (right now we don't track range scans at all),
but also at the "prepared statement" level as it were:
{{{SELECT x FROM foo WHERE key = ?}}} would be one query no matter what the ?
is, but {{{SELECT y FROM foo WHERE key = ?}}} would be different. {{{SELECT
x..y FROM foo WHERE key = ?}}} would be another, as would {{{SELECT x FROM foo
WHERE key = ? AND bar= ?}}}. (But {{{SELECT x FROM foo WHERE bar = ? AND key =
?}}} would be identical to the former, of course.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3451) estimated row sizes regression
estimated row sizes regression -- Key: CASSANDRA-3451 URL: https://issues.apache.org/jira/browse/CASSANDRA-3451 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 1.0.0 Reporter: Jonathan Ellis Assignee: Jonathan Ellis Fix For: 1.0.2 CASSANDRA-2753 broke the histogram collection; it got the histogram for column count (which can go up to 2B) switched with the one for row size in bytes (which goes up to ~1.5PB). So any row over 2GB, will break things. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3449) Missing null check in digest retry part of read path
Missing null check in digest retry part of read path Key: CASSANDRA-3449 URL: https://issues.apache.org/jira/browse/CASSANDRA-3449 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 1.0.0 Reporter: Jonathan Ellis Assignee: Jonathan Ellis Fix For: 1.0.2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3445) recognize that "SELECT first ... *" isn't really "SELECT *"
recognize that "SELECT first ... *" isn't really "SELECT *" --- Key: CASSANDRA-3445 URL: https://issues.apache.org/jira/browse/CASSANDRA-3445 Project: Cassandra Issue Type: Bug Components: API Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 1.1 QueryProcessor includes the row key in "first *" because it mistakenly thinks the full row is being requested. "first *" should really be treated like a slice. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3442) TTL histogram for sstable metadata
TTL histogram for sstable metadata -- Key: CASSANDRA-3442 URL: https://issues.apache.org/jira/browse/CASSANDRA-3442 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Jonathan Ellis Priority: Minor Under size-tiered compaction, you can generate large sstables that compact infrequently. With expiring columns mixed in, we could waste a lot of space in this situation. If we kept a TTL EstimatedHistogram in the sstable metadata, we could do a single-sstable compaction aginst sstables with over 20% (?) expired data. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3440) local writes timing out cause attempt to hint to self
local writes timing out cause attempt to hint to self
-
Key: CASSANDRA-3440
URL: https://issues.apache.org/jira/browse/CASSANDRA-3440
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 1.0.0
Reporter: Jonathan Ellis
Assignee: Jonathan Ellis
Fix For: 1.0.2
As reported by Ramash Natarajan on the mailing list:
{noformat}
We have a 8 node cassandra cluster running 1.0.1. After running a load
test for a day we are seeing this exception in system.log file.
ERROR [EXPIRING-MAP-TIMER-1] 2011-11-01 13:20:45,350
AbstractCassandraDaemon.java (line 133) Fatal exception in thread
Thread[EXPIRING-MAP-TIMER-1,5,main]
java.lang.AssertionError: /10.19.102.12
at
org.apache.cassandra.service.StorageProxy.scheduleLocalHint(StorageProxy.java:339)
at
org.apache.cassandra.net.MessagingService.scheduleMutationHint(MessagingService.java:201)
at
org.apache.cassandra.net.MessagingService.access$500(MessagingService.java:64)
at
org.apache.cassandra.net.MessagingService$2.apply(MessagingService.java:175)
at
org.apache.cassandra.net.MessagingService$2.apply(MessagingService.java:152)
at org.apache.cassandra.utils.ExpiringMap$1.run(ExpiringMap.java:89)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3439) Update cassandra.apache.org front page
Update cassandra.apache.org front page -- Key: CASSANDRA-3439 URL: https://issues.apache.org/jira/browse/CASSANDRA-3439 Project: Cassandra Issue Type: Improvement Components: Documentation & website Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor The Cassandra front page is getting a bit long in the tooth. Some links are dead and the rest are almost two years old. And frankly I'd like to distance us from Facebook since they haven't been involved for years. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3437) invalidate / unregisterSSTables is confused
invalidate / unregisterSSTables is confused --- Key: CASSANDRA-3437 URL: https://issues.apache.org/jira/browse/CASSANDRA-3437 Project: Cassandra Issue Type: Bug Components: Core Reporter: Jonathan Ellis Assignee: Jonathan Ellis Fix For: 1.0.2 invalidate doesn't call unregisterSSTables, and vice versa, making it easy to get yourself into a situation that "shouldn't happen." This is causing test failures post-CASSANDRA-3116. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3430) Break Big Compaction Lock apart
Break Big Compaction Lock apart --- Key: CASSANDRA-3430 URL: https://issues.apache.org/jira/browse/CASSANDRA-3430 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 1.0.2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3429) Fix truncate/compaction race without locking
Fix truncate/compaction race without locking Key: CASSANDRA-3429 URL: https://issues.apache.org/jira/browse/CASSANDRA-3429 Project: Cassandra Issue Type: Bug Components: Core Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 1.0.2 See CASSANDRA-3399 for original problem description. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3423) Log useful information about CF configuration
Log useful information about CF configuration - Key: CASSANDRA-3423 URL: https://issues.apache.org/jira/browse/CASSANDRA-3423 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 0.8.8, 1.0.2 It would help troubleshooting if we logged pertinent details about CF configuration (particularly cache size) on startup. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3410) inconsistent rejection of CL.ANY on reads
inconsistent rejection of CL.ANY on reads - Key: CASSANDRA-3410 URL: https://issues.apache.org/jira/browse/CASSANDRA-3410 Project: Cassandra Issue Type: Bug Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 1.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3393) report compression ratio in CFSMBean
report compression ratio in CFSMBean Key: CASSANDRA-3393 URL: https://issues.apache.org/jira/browse/CASSANDRA-3393 Project: Cassandra Issue Type: Improvement Components: Tools Affects Versions: 1.0.0 Reporter: Jonathan Ellis Assignee: Pavel Yaskevich Priority: Minor Fix For: 1.0.1 (should expose in nodetool cfstats as well) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3389) Evaluate CSLM alternatives for improved cache or GC performance
Evaluate CSLM alternatives for improved cache or GC performance --- Key: CASSANDRA-3389 URL: https://issues.apache.org/jira/browse/CASSANDRA-3389 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Jonathan Ellis Assignee: Brandon Williams Priority: Minor Fix For: 1.1 Ben Manes commented on http://www.datastax.com/dev/blog/whats-new-in-cassandra-1-0-performance that it's worth evaluating https://github.com/mspiegel/lockfreeskiptree and https://github.com/nbronson/snaptree as CSLM replacements. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3386) Avoid lock contention in hint rows
Avoid lock contention in hint rows -- Key: CASSANDRA-3386 URL: https://issues.apache.org/jira/browse/CASSANDRA-3386 Project: Cassandra Issue Type: Improvement Components: Core Affects Versions: 0.7.0 Reporter: Jonathan Ellis Assignee: Jonathan Ellis Fix For: 0.8.8, 1.0.1 As pointed out by Yang in CASSANDRA-3385, hint writes are keyed by target IP, to make replay efficient. However, this means that we'll hit a lot of lock contention in table.apply where we synchronize for potential index updates. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3377) correct dropped messages logging
correct dropped messages logging Key: CASSANDRA-3377 URL: https://issues.apache.org/jira/browse/CASSANDRA-3377 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 0.8.4 Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 0.8.8 CASSANDRA-3004 switched MessagingService back to logging only "recent" dropped messages instead of server lifetime totals, but the log message was not updated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3376) Track buffer cache hit rate with mincore
Track buffer cache hit rate with mincore Key: CASSANDRA-3376 URL: https://issues.apache.org/jira/browse/CASSANDRA-3376 Project: Cassandra Issue Type: New Feature Reporter: Jonathan Ellis Priority: Minor We could use mincore on, say, 1% of reads to be able to report actual buffer cache hit rate. This would be useful when troubleshooting slow reads, e.g., are reads to CF X slow because it's hitting disk, or because there are a lot of tombstones in the row? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3363) Allow one leveled compaction task to kick off another
Allow one leveled compaction task to kick off another - Key: CASSANDRA-3363 URL: https://issues.apache.org/jira/browse/CASSANDRA-3363 Project: Cassandra Issue Type: Improvement Components: Core Affects Versions: 1.0.0 Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 1.0.1 Leveled compaction wants to prevent multiple tasks from running at once, but this check also defeats the "kick off another compaction if there is more work to do" code in CompactionTask. So currently LCS relies completely on the every-five-minutes compaction check, which is not enough to keep up with heavy insert load. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3362) allow sub-row repair
allow sub-row repair Key: CASSANDRA-3362 URL: https://issues.apache.org/jira/browse/CASSANDRA-3362 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Jonathan Ellis Assignee: Sylvain Lebresne Priority: Minor With large rows, it would be nice to not have to send an entire row if a small part is out of sync. Could we use the row index blocks as repair atoms instead of the full row? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3359) snapshot should include manifest under leveledcompaction
snapshot should include manifest under leveledcompaction Key: CASSANDRA-3359 URL: https://issues.apache.org/jira/browse/CASSANDRA-3359 Project: Cassandra Issue Type: Improvement Components: Core Affects Versions: 1.0.0 Reporter: Jonathan Ellis Assignee: Pavel Yaskevich Fix For: 1.0.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3333) remove more copies from read/write network path
remove more copies from read/write network path --- Key: CASSANDRA- URL: https://issues.apache.org/jira/browse/CASSANDRA- Project: Cassandra Issue Type: Improvement Components: Core Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 1.0.1 RowMutation.serializedBuffer and ReadVerbHandler both do an extra copy of the serialized data. We can avoid this be pre-computing the serialized size and allocating an appropriate buffer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3330) Improve CompactionTask extensibility
Improve CompactionTask extensibility Key: CASSANDRA-3330 URL: https://issues.apache.org/jira/browse/CASSANDRA-3330 Project: Cassandra Issue Type: Improvement Components: Core Affects Versions: 1.0.0 Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 1.0.0 CompactionTask is still fairly coupled to SizeTieredCompaction, including some ugly casting. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3329) make HSHA the default Thrift server
make HSHA the default Thrift server --- Key: CASSANDRA-3329 URL: https://issues.apache.org/jira/browse/CASSANDRA-3329 Project: Cassandra Issue Type: Improvement Components: API Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 1.0.0 HSHA has been an option since 0.8.3 (CASSANDRA-1405) and has been stable. Besides making possible lots of unpooled connections such as are common in some environments (*cough* PHP), we've seen EC2 in particular have trouble with lots of threads (CASSANDRA-2170). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CASSANDRA-3328) make leveled compaction suck less for insert-heavy workloads
make leveled compaction suck less for insert-heavy workloads Key: CASSANDRA-3328 URL: https://issues.apache.org/jira/browse/CASSANDRA-3328 Project: Cassandra Issue Type: Improvement Reporter: Jonathan Ellis Priority: Minor In insert-heavy workloads, leveled compaction needs to do a lot of "promotion" from one level to a higher one, where the higher level has no overlapping sstables. We can optimize a lot of these away by not bothering to rewrite sstables that are younger than GCGraceSeconds. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
