date:20130205

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The ClientOptions page has been changed by Max Penet:
http://wiki.apache.org/cassandra/ClientOptions?action=diffrev1=163rev2=164

* Helenus: https://github.com/simplereach/helenus
   * Clojure
* clj-hector: https://github.com/pingles/clj-hector
+   * casyn: https://github.com/mpenet/casyn
   * .NET
* Aquiles: http://aquiles.codeplex.com/
* Cassandraemon: http://cassandraemon.codeplex.com/

[jira] [Updated] (CASSANDRA-4464) expose 2I CFs to the rest of nodetool

2013-02-05 Thread Jason Brown (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Brown updated CASSANDRA-4464:
---

Attachment: 4464-v2.patch

Rebased against branch cassandra-1.2.

 expose 2I CFs to the rest of nodetool
 -

 Key: CASSANDRA-4464
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4464
 Project: Cassandra
  Issue Type: New Feature
  Components: Tools
Reporter: Jonathan Ellis
Assignee: Jason Brown
Priority: Minor
 Fix For: 1.2.2

 Attachments: 4464.txt, 4464-v1.patch, 4464-v2.patch


 This was begun in CASSANDRA-4063.  We should extend it to scrub as well, and 
 probably compact since any sane way to do it for scrub should give the other 
 for free.
 Not sure how easy these will be since they go through CompactionManager via 
 StorageProxy.  I think getValidColumnFamilies could be updated to check for 
 index CFs with dot notation.
 (Other operations like flush or snapshot don't make sense for 2I CFs in 
 isolation of their parent.)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Cassandra Wiki] Trivial Update of EIBKathy by EIBKathy

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The EIBKathy page has been changed by EIBKathy:
http://wiki.apache.org/cassandra/EIBKathy

New page:
Howdy !! I am BOBBYE JIMENEZ. I am from Gainesville. I might take night 
schooling in The Fuzzy Institute of Strong People built at Port St.BR
BR
Lucie. I work as a Police Inspector. I like Reading To The Elderly. My dad name 
is Stephen  and he is a Economist. My momy is a Therapist.BR
BR
Look into my page [[http://www.aldorabag.com|chanel outlet]]

[Cassandra Wiki] Trivial Update of KVVVeroni by KVVVeroni

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The KVVVeroni page has been changed by KVVVeroni:
http://wiki.apache.org/cassandra/KVVVeroni

New page:
Hello !! I am RONDA COLLIER. I have a job as Alderman. My dad name is Nathaniel 
 and he is a Engine-driver.BR
My mom is a Stock-breeder.BR
BR
Check out my web blog: 
[[http://www.cleanscreenxcel.com/cheapmonsterbeatsbydre.html|dr dre earphones]]

[Cassandra Wiki] Trivial Update of KVVVeroni by KVVVeroni

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The KVVVeroni page has been changed by KVVVeroni:
http://wiki.apache.org/cassandra/KVVVeroni?action=diffrev1=1rev2=2

- Hello !! I am RONDA COLLIER. I have a job as Alderman. My dad name is 
Nathaniel  and he is a Engine-driver.BR
- My mom is a Stock-breeder.BR
+ Hey guys !! I am KARMA NEWTON. I work as a Coach.BR
+ My daddy name is Bryan  and he is a Fowler. My mummy is a Guitarist.BR
  BR
- Check out my web blog: 
[[http://www.cleanscreenxcel.com/cheapmonsterbeatsbydre.html|dr dre earphones]]
+ Feel free to visit my website; 
[[http://www.unitedchem.com/beatbydre.aspx|monster earphones]]

[Cassandra Wiki] Trivial Update of beats_headphones_review_z0k2 by KVVVeroni

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The beats_headphones_review_z0k2 page has been changed by KVVVeroni:
http://wiki.apache.org/cassandra/beats_headphones_review_z0k2

New page:
[[http://www.unitedchem.com/beatbydre.aspx|http://www.unitedchem.com/beatbydre.aspx]]BR
[[http://www.unitedchem.com/beatbydre.aspx|cheap beats by dre]]BR
[[http://www.unitedchem.com/beatbydre.aspx|beats by dre cheap]]BR
[[http://www.unitedchem.com/beatbydre.aspx|monster earphones]]BR
After a quick bone fragments physician, Zhang Ming's adjustable rate mortgage 
is not, just on holiday struggling to give good results, have to have a full 
week others in your home, however she laid off six months wouldn't acquire 
deliver the results, made from difficulty calm down in the house.Go away a 
healthcare facility a pair of returning, ultra violet rays has been plunging 
xishan. Following your residence Zhang Ming obediently rest, look to the 
formula. Another worry about, care not necessarily loudly reprimand angrily to 
schedule an appointment girlfriend, lest irritate the tiny starlet, then can 
lead to a superior pumping.Picture is happy to return, wouldn't expect to have 
it to acquire this situation at present, examining issues sister, idea in the 
beginning meant to Mother nourishment, it's possible that only less expensive 
this unique lazy dad.If Fang Yiyun tidy right up factor, numerous crazy items 
to inquire where is any, situation composed an excuse, testified that Lin Zekai 
can't end feeding on offered your ex, Fang Yiyun realized this Lin Zekai 
wonderful pals, as well as the frame of mind is not superb, hardly any silt 
doubt.Pick-up monetary management goods, Fang Yiyun started out barbecuing, 
equation drawn the out, evaluate her haggard physical appearance, heartbeat, 
more were not able to benefit though leaked gloomy.Half inch Great aunt, I will 
be returning, include institution another day. Fang Yiyun odour conversation, 
along with a not willing, to make sure you keep the best way: In Cheng Cheng, 
in your dinner party, it's going to be alright.  Virtually no, go home have a 
thing. Centimeter Then, picture came five hundred yuan out of the pocket, 
planned to prefer to eliminate 299, enter my personal aunt's fretting hand, 
process: In great aunt, this money you become, don't offer big brother watched, 
realize? Fang Yiyun is much more astonished, think it is her, option: Half 
inch Cheng Cheng, a lot of capital anyone exactly where?  These days We came 
across the clear way of a new foreigner, My partner and i acquired them to the 
location, these thanked me provided me a bundle. In . See my own mother along 
with a cynical take a look, give preference to means: In mother, equations 
established your mind sleeping, these funds is definitely thoroughly clean. To 
notice your ex point out, Fang Yiyun the following just simply half-believe in 
the lower, see she's very quickly, and also support the area: In . almond will 
be in a position in the near future, which means that be for lunch. 
CentimeterBR
[[http://www.cleanscreenxcel.com/cheapmonsterbeatsbydre.html|http://www.cleanscreenxcel.com/cheapmonsterbeatsbydre.html]]BR
[[http://www.cleanscreenxcel.com/cheapmonsterbeatsbydre.html|cheap beats by 
dre]]BR
[[http://www.cleanscreenxcel.com/cheapmonsterbeatsbydre.html|beats by dre 
cheap]]BR
[[http://www.cleanscreenxcel.com/cheapmonsterbeatsbydre.html|beat by dre]]

[jira] [Updated] (CASSANDRA-5222) OOM Exception during repair session with LeveledCompactionStrategy


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Sobolev updated CASSANDRA-5222:


Attachment: sstablescanner.png

 OOM Exception during repair session with LeveledCompactionStrategy
 --

 Key: CASSANDRA-5222
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5222
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.1.6
 Environment: 3Gb Heap(12Gb per node RAM)
 36 nodes, 0.9 Tb of data per node, Leveled compaction strategy, SSTable size 
 =100Mb
Reporter: Ivan Sobolev
Priority: Critical
 Attachments: sstablescanner.png


 1.8 Gb of heap is consumed with 12k SSTableBoundedScanner * 140kbytes

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CASSANDRA-5222) OOM Exception during repair session with LeveledCompactionStrategy

Ivan Sobolev created CASSANDRA-5222:
---

 Summary: OOM Exception during repair session with 
LeveledCompactionStrategy
 Key: CASSANDRA-5222
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5222
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.1.6
 Environment: 3Gb Heap(12Gb per node RAM)
36 nodes, 0.9 Tb of data per node, Leveled compaction strategy, SSTable size 
=100Mb

Reporter: Ivan Sobolev
Priority: Critical
 Attachments: sstablescanner.png

1.8 Gb of heap is consumed with 12k SSTableBoundedScanner * 140kbytes

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CASSANDRA-5222) OOM Exception during repair session with LeveledCompactionStrategy


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jonathan Ellis resolved CASSANDRA-5222.
---

Resolution: Cannot Reproduce

Sounds to me like you're not actually running 1.1.6.  Look at 
LeveledCompactionStrategy.getScanners; it will only open one scanner per level, 
except for L0.  (And we guarantee that only up to MAX_COMPACTING_L0=32 L0 
candiates participate, see LeveledManifest.getCompactionCandidates.)

 OOM Exception during repair session with LeveledCompactionStrategy
 --

 Key: CASSANDRA-5222
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5222
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.1.6
 Environment: 3Gb Heap(12Gb per node RAM)
 36 nodes, 0.9 Tb of data per node, Leveled compaction strategy, SSTable size 
 =100Mb
Reporter: Ivan Sobolev
Priority: Critical
 Attachments: sstablescanner.png


 1.8 Gb of heap is consumed with 12k SSTableBoundedScanner * 140kbytes

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CASSANDRA-5223) Secondary index doesn't get repaired

Alexei Bakanov created CASSANDRA-5223:
-

 Summary: Secondary index doesn't get repaired
 Key: CASSANDRA-5223
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5223
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.2.1
 Environment: Ubuntu dtest, laptop with 8G RAM
Reporter: Alexei Bakanov


Looks like secondary indexes don't get repaired by any of the Cassandra repair 
mechanisms for NetworkTopologyStrategy. SimpleStrategy however works fine.

The issue started as a mail to Cassandra userlist: 
http://article.gmane.org/gmane.comp.db.cassandra.user/30909
I striped reproduction recipe down and made a d-test which inserts two rows 
into a cluster of two nodes, where the first node goes down after the first 
insert and goes back up after the second insert. Secondary index doesn't get 
repaired by neither hinted-handoff, read repair, nor manual 'repair' operation 
which the d-test triggers before reading the data.
Moreover the second row is not visible in the index unless I do CL.ALL read or 
drop/create the index.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Cassandra Wiki] Trivial Update of ClarkABN by ClarkABN

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The ClarkABN page has been changed by ClarkABN:
http://wiki.apache.org/cassandra/ClarkABN

New page:
Hey !! My name is SOFIA WALSH. I reside in McAllen. I am turning 32.BR
I want to become a Navigator. I am a fan of matchboxes. My dad name is Chad  
and he is a Lifeguard. My mother is a Stuntman.BR
BR
my web blog; [[http://michael-kors-shoes.blinkweb.com|michael kors outlet]]

[jira] [Updated] (CASSANDRA-5223) Secondary index doesn't get repaired


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexei Bakanov updated CASSANDRA-5223:
--

Attachment: secondary_index_repair_test.py

d-test script to test how repair works for secondary indexes

 Secondary index doesn't get repaired
 

 Key: CASSANDRA-5223
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5223
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.2.1
 Environment: Ubuntu dtest, laptop with 8G RAM
Reporter: Alexei Bakanov
 Attachments: secondary_index_repair_test.py


 Looks like secondary indexes don't get repaired by any of the Cassandra 
 repair mechanisms for NetworkTopologyStrategy. SimpleStrategy however works 
 fine.
 The issue started as a mail to Cassandra userlist: 
 http://article.gmane.org/gmane.comp.db.cassandra.user/30909
 I striped reproduction recipe down and made a d-test which inserts two rows 
 into a cluster of two nodes, where the first node goes down after the first 
 insert and goes back up after the second insert. Secondary index doesn't get 
 repaired by neither hinted-handoff, read repair, nor manual 'repair' 
 operation which the d-test triggers before reading the data.
 Moreover the second row is not visible in the index unless I do CL.ALL read 
 or drop/create the index.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-5222) OOM Exception during repair session with LeveledCompactionStrategy


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571296#comment-13571296
 ] 

Jonathan Ellis commented on CASSANDRA-5222:
---

Note that your heap dump is full of SSTableBoundedScanner, which (in 1.1.1+) is 
only used by L0 or STCS.  Otherwise LeveledScanner is used.  So it's also 
possible this was set back to STCS by mistake.

 OOM Exception during repair session with LeveledCompactionStrategy
 --

 Key: CASSANDRA-5222
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5222
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.1.6
 Environment: 3Gb Heap(12Gb per node RAM)
 36 nodes, 0.9 Tb of data per node, Leveled compaction strategy, SSTable size 
 =100Mb
Reporter: Ivan Sobolev
Priority: Critical
 Attachments: sstablescanner.png


 1.8 Gb of heap is consumed with 12k SSTableBoundedScanner * 140kbytes

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Cassandra Wiki] Trivial Update of LucindaHi by LucindaHi

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The LucindaHi page has been changed by LucindaHi:
http://wiki.apache.org/cassandra/LucindaHi

New page:
Hi !! The name is NOBUKO MERCADO. I am from Plano.BRThis summer iam going 
to be 25. I go to night school at The Professional Preparatory of Useful 
Education which has a branch in Leominster. My hobby is Fast cars. My papa name 
is Ross  and he is a Coroner. My mummy is a Choreographer.BRBRFeel free 
to visit my website [[http://www.addiehandbags.com|gucci outlet online]]

[jira] [Commented] (CASSANDRA-5222) OOM Exception during repair session with LeveledCompactionStrategy


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571299#comment-13571299
 ] 

Ivan Sobolev commented on CASSANDRA-5222:
-

Seems, all sstables appear there:
{quote}ls | grep Data | wc -l 
   10760{quote}

 OOM Exception during repair session with LeveledCompactionStrategy
 --

 Key: CASSANDRA-5222
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5222
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.1.6
 Environment: 3Gb Heap(12Gb per node RAM)
 36 nodes, 0.9 Tb of data per node, Leveled compaction strategy, SSTable size 
 =100Mb
Reporter: Ivan Sobolev
Priority: Critical
 Attachments: sstablescanner.png


 1.8 Gb of heap is consumed with 12k SSTableBoundedScanner * 140kbytes

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-5222) OOM Exception during repair session with LeveledCompactionStrategy


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571301#comment-13571301
 ] 

Ivan Sobolev commented on CASSANDRA-5222:
-

{quote}Sounds to me like you're not actually running 1.1.6.
[root@da1-node30 chunks]# nodetool -h `hostname` version
ReleaseVersion: 1.1.6

That's DataStax version and it may differ a bit - not sure how do the versions 
correlate.

 OOM Exception during repair session with LeveledCompactionStrategy
 --

 Key: CASSANDRA-5222
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5222
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.1.6
 Environment: 3Gb Heap(12Gb per node RAM)
 36 nodes, 0.9 Tb of data per node, Leveled compaction strategy, SSTable size 
 =100Mb
Reporter: Ivan Sobolev
Priority: Critical
 Attachments: sstablescanner.png


 1.8 Gb of heap is consumed with 12k SSTableBoundedScanner * 140kbytes

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Comment Edited] (CASSANDRA-5222) OOM Exception during repair session with LeveledCompactionStrategy


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571301#comment-13571301
 ] 

Ivan Sobolev edited comment on CASSANDRA-5222 at 2/5/13 1:48 PM:
-

{quote}Sounds to me like you're not actually running 1.1.6.
[root@da1-node30 chunks]# nodetool -h `hostname` version
ReleaseVersion: 1.1.6{quote}

That's DataStax version and it may differ a bit - not sure how do the versions 
correlate.

  was (Author: soboleiv):
{quote}Sounds to me like you're not actually running 1.1.6.
[root@da1-node30 chunks]# nodetool -h `hostname` version
ReleaseVersion: 1.1.6

That's DataStax version and it may differ a bit - not sure how do the versions 
correlate.
  
 OOM Exception during repair session with LeveledCompactionStrategy
 --

 Key: CASSANDRA-5222
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5222
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.1.6
 Environment: 3Gb Heap(12Gb per node RAM)
 36 nodes, 0.9 Tb of data per node, Leveled compaction strategy, SSTable size 
 =100Mb
Reporter: Ivan Sobolev
Priority: Critical
 Attachments: sstablescanner.png


 1.8 Gb of heap is consumed with 12k SSTableBoundedScanner * 140kbytes

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Comment Edited] (CASSANDRA-5222) OOM Exception during repair session with LeveledCompactionStrategy


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571301#comment-13571301
 ] 

Ivan Sobolev edited comment on CASSANDRA-5222 at 2/5/13 1:50 PM:
-

{quote}Sounds to me like you're not actually running 1.1.6.
[root@da1-node30 chunks]# nodetool -h `hostname` version
ReleaseVersion: 1.1.6{quote}

That's DataStax version and it may differ a bit - not sure how do the versions 
correlate.

Upd: should be the same: 
http://www.datastax.com/dev/blog/datastax-community-edition-1-1-6-now-available

  was (Author: soboleiv):
{quote}Sounds to me like you're not actually running 1.1.6.
[root@da1-node30 chunks]# nodetool -h `hostname` version
ReleaseVersion: 1.1.6{quote}

That's DataStax version and it may differ a bit - not sure how do the versions 
correlate.
  
 OOM Exception during repair session with LeveledCompactionStrategy
 --

 Key: CASSANDRA-5222
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5222
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.1.6
 Environment: 3Gb Heap(12Gb per node RAM)
 36 nodes, 0.9 Tb of data per node, Leveled compaction strategy, SSTable size 
 =100Mb
Reporter: Ivan Sobolev
Priority: Critical
 Attachments: sstablescanner.png


 1.8 Gb of heap is consumed with 12k SSTableBoundedScanner * 140kbytes

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-5222) OOM Exception during repair session with LeveledCompactionStrategy


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571306#comment-13571306
 ] 

Ivan Sobolev commented on CASSANDRA-5222:
-

{quote}So it's also possible this was set back to STCS by mistake.{quote}
You mean SizeTieredCompactionStrategy? 

Sstable's *-Data files are up to 100Mb

{quote}[default@chunks] describe chunks;
ColumnFamily: chunks
  Key Validation Class: org.apache.cassandra.db.marshal.UTF8Type
  Default column value validator: org.apache.cassandra.db.marshal.BytesType
  Columns sorted by: org.apache.cassandra.db.marshal.BytesType
  GC grace seconds: 864000
  Compaction min/max thresholds: 4/32
  Read repair chance: 0.1
  DC Local Read repair chance: 0.0
  Replicate on write: true
  Caching: KEYS_ONLY
  Bloom Filter FP chance: default
  Built indexes: []
  Compaction Strategy: 
org.apache.cassandra.db.compaction.LeveledCompactionStrategy
  Compaction Strategy Options:
sstable_size_in_mb: 100
  Compression Options:
sstable_compression: 
org.apache.cassandra.io.compress.SnappyCompressor{quote}

Anything else I could check?

 OOM Exception during repair session with LeveledCompactionStrategy
 --

 Key: CASSANDRA-5222
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5222
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.1.6
 Environment: 3Gb Heap(12Gb per node RAM)
 36 nodes, 0.9 Tb of data per node, Leveled compaction strategy, SSTable size 
 =100Mb
Reporter: Ivan Sobolev
Priority: Critical
 Attachments: sstablescanner.png


 1.8 Gb of heap is consumed with 12k SSTableBoundedScanner * 140kbytes

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-5196) IllegalStateException thrown when running new installation with old data directories

2013-02-05 Thread Robbie Strickland (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571318#comment-13571318
 ] 

Robbie Strickland commented on CASSANDRA-5196:
--

In my case the directories were owned by cassandra and the service was 
started as cassandra using init.  Even starting as root resulted in the same 
failure.  Only deleting the directories entirely resolved the issue.  This 
worked in my case because it was an old installation and I didn't need the 
data, but it took me a while to figure this out since the exception was so 
misleading.

 IllegalStateException thrown when running new installation with old data 
 directories
 

 Key: CASSANDRA-5196
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5196
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.2.1
 Environment: CentOS 5.5
Reporter: Robbie Strickland
Assignee: Aleksey Yeschenko
Priority: Minor

 If you install 1.2.1 when there are existing data directories, the scrub 
 operation fails, throwing this exception:
 ERROR [main] 2013-01-29 15:05:06,564 FileUtils.java (line 373) Stopping the 
 gossiper and the RPC server
 ERROR [main] 2013-01-29 15:05:06,564 CassandraDaemon.java (line 387) 
 Exception encountered during startup
 java.lang.IllegalStateException: No configured daemon
   at 
 org.apache.cassandra.service.StorageService.stopRPCServer(StorageService.java:314)
   at 
 org.apache.cassandra.io.util.FileUtils.handleFSError(FileUtils.java:375)
   at org.apache.cassandra.db.Directories.init(Directories.java:113)
   at org.apache.cassandra.db.Directories.create(Directories.java:91)
   at 
 org.apache.cassandra.db.ColumnFamilyStore.scrubDataDirectories(ColumnFamilyStore.java:403)
   at 
 org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:174)
   at 
 org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:370)
   at 
 org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:413)
 This condition should produce a more reasonable exception.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-5222) OOM Exception during repair session with LeveledCompactionStrategy


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Sobolev updated CASSANDRA-5222:


Attachment: chunks.json

 OOM Exception during repair session with LeveledCompactionStrategy
 --

 Key: CASSANDRA-5222
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5222
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.1.6
 Environment: 3Gb Heap(12Gb per node RAM)
 36 nodes, 0.9 Tb of data per node, Leveled compaction strategy, SSTable size 
 =100Mb
Reporter: Ivan Sobolev
Priority: Critical
 Attachments: chunks.json, sstablescanner.png


 1.8 Gb of heap is consumed with 12k SSTableBoundedScanner * 140kbytes

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-5038) LZ4Compressor

2013-02-05 Thread T Jake Luciani (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571321#comment-13571321
 ] 

T Jake Luciani commented on CASSANDRA-5038:
---

I've tried using the JNI hooks (built manually) and I don't see any difference 
in latency compared to misc.Unsafe.

The current version as submitted is good.

I did want to post a side by side comparison to java snappy but haven't had a 
chance.

 LZ4Compressor
 -

 Key: CASSANDRA-5038
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5038
 Project: Cassandra
  Issue Type: New Feature
  Components: Core
Reporter: T Jake Luciani
Priority: Minor
 Fix For: 1.2.2

 Attachments: CASSANDRA-5038.patch, CASSANDRA-5038.patch, 
 LZ4Compressor.java, lz4-java.jar


 LZ4 is a new compression algo that's ~2x faster than Snappy.
 [~jpountz] has written a nice java port which includes a misc.Unsafe version 
 that performs = than our java snappy version.
 Details at http://blog.jpountz.net/post/28092106032/wow-lz4-is-fast
 The nice thing is this should work with java7 and be more portable.
 We can also fallback the pure java impl

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-5222) OOM Exception during repair session with LeveledCompactionStrategy


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571326#comment-13571326
 ] 

Ivan Sobolev commented on CASSANDRA-5222:
-

Do you think backlogged L0 may lead to such effects? Currently I can see 3k 
tables there, not sure if it went from 12k to 3k that quick.

 OOM Exception during repair session with LeveledCompactionStrategy
 --

 Key: CASSANDRA-5222
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5222
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.1.6
 Environment: 3Gb Heap(12Gb per node RAM)
 36 nodes, 0.9 Tb of data per node, Leveled compaction strategy, SSTable size 
 =100Mb
Reporter: Ivan Sobolev
Priority: Critical
 Attachments: chunks.json, sstablescanner.png


 1.8 Gb of heap is consumed with 12k SSTableBoundedScanner * 140kbytes

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-5222) OOM Exception during repair session with LeveledCompactionStrategy


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571331#comment-13571331
 ] 

Ivan Sobolev commented on CASSANDRA-5222:
-

Another node died. Can see exactly 12k L0 tables there, seems we're just under 
capacity with current setup.

 OOM Exception during repair session with LeveledCompactionStrategy
 --

 Key: CASSANDRA-5222
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5222
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.1.6
 Environment: 3Gb Heap(12Gb per node RAM)
 36 nodes, 0.9 Tb of data per node, Leveled compaction strategy, SSTable size 
 =100Mb
Reporter: Ivan Sobolev
Priority: Critical
 Attachments: chunks.json, sstablescanner.png


 1.8 Gb of heap is consumed with 12k SSTableBoundedScanner * 140kbytes

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Reopened] (CASSANDRA-5222) OOM Exception during repair session with LeveledCompactionStrategy


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jonathan Ellis reopened CASSANDRA-5222:
---

  Assignee: Yuki Morishita

Aha... repair has to examine each sstable, it can't limit itself to 32 in L0.  
So having L0 fall behind will screw you over like this.

Only quick fix I can think of is to fail repair until L0 gets under control -- 
say, 2x MAX_COMPACTING_L0.

 OOM Exception during repair session with LeveledCompactionStrategy
 --

 Key: CASSANDRA-5222
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5222
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.1.6
 Environment: 3Gb Heap(12Gb per node RAM)
 36 nodes, 0.9 Tb of data per node, Leveled compaction strategy, SSTable size 
 =100Mb
Reporter: Ivan Sobolev
Assignee: Yuki Morishita
Priority: Critical
 Attachments: chunks.json, sstablescanner.png


 1.8 Gb of heap is consumed with 12k SSTableBoundedScanner * 140kbytes

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-5222) OOM Exception during repair session with LeveledCompactionStrategy


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jonathan Ellis updated CASSANDRA-5222:
--

 Reviewer: jbellis
 Priority: Major  (was: Critical)
Affects Version/s: (was: 1.1.6)
   1.0.0
Fix Version/s: 1.1.10

 OOM Exception during repair session with LeveledCompactionStrategy
 --

 Key: CASSANDRA-5222
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5222
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.0.0
 Environment: 3Gb Heap(12Gb per node RAM)
 36 nodes, 0.9 Tb of data per node, Leveled compaction strategy, SSTable size 
 =100Mb
Reporter: Ivan Sobolev
Assignee: Yuki Morishita
 Fix For: 1.1.10

 Attachments: chunks.json, sstablescanner.png


 1.8 Gb of heap is consumed with 12k SSTableBoundedScanner * 140kbytes

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-2103) expiring counter columns

2013-02-05 Thread Nikolay (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571345#comment-13571345
 ] 

Nikolay commented on CASSANDRA-2103:


What about following use case:

First time when you increase the counter (e.g. counter does not exists), you 
supply TTL.
Then counter is created with this TTL.

Next, the TTL is ignored, until counter is alive.

This means if you create it with TTL 1 week, counter will be alive for a 
week, then it expires and then it is created again , and assuming you still 
give TTL 1 week, counter is like resetting.

In this case implementation will not be that hard I believe, since all replicas 
will have consolidated expire date?

 expiring counter columns
 

 Key: CASSANDRA-2103
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2103
 Project: Cassandra
  Issue Type: New Feature
  Components: Core
Affects Versions: 0.8 beta 1
Reporter: Kelvin Kakugawa
 Attachments: 0001-CASSANDRA-2103-expiring-counters-logic-tests.patch


 add ttl functionality to counter columns.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[2/7] git commit: avoid no-op caching of byte[] on commitlog append patch by jbellis; reviewed by yukim for CASSANDRA-5199

avoid no-op caching of byte[] on commitlog append
patch by jbellis; reviewed by yukim for CASSANDRA-5199


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/1c79426a
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/1c79426a
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/1c79426a

Branch: refs/heads/trunk
Commit: 1c79426ab86a1d26e7214d8d86b8eb24d67c0ab0
Parents: 75d0f7a
Author: Jonathan Ellis jbel...@apache.org
Authored: Tue Feb 5 15:40:45 2013 +0100
Committer: Jonathan Ellis jbel...@apache.org
Committed: Tue Feb 5 15:40:45 2013 +0100

--
 CHANGES.txt|1 +
 src/java/org/apache/cassandra/db/RowMutation.java  |   36 +--
 .../cassandra/db/commitlog/CommitLogSegment.java   |3 +-
 3 files changed, 4 insertions(+), 36 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/1c79426a/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index e0e8079..5e661ae 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
 1.2.2
+ * avoid no-op caching of byte[] on commitlog append (CASSANDRA-5199)
  * more robust solution to incomplete compactions + counters (CASSANDRA-5151)
  * fix symlinks under data dir not working (CASSANDRA-5185)
  * fix bug in compact storage metadata handling (CASSANDRA-5189)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/1c79426a/src/java/org/apache/cassandra/db/RowMutation.java
--
diff --git a/src/java/org/apache/cassandra/db/RowMutation.java 
b/src/java/org/apache/cassandra/db/RowMutation.java
index a8e845d..5064c65 100644
--- a/src/java/org/apache/cassandra/db/RowMutation.java
+++ b/src/java/org/apache/cassandra/db/RowMutation.java
@@ -18,7 +18,6 @@
 package org.apache.cassandra.db;
 
 import java.io.DataInput;
-import java.io.DataInputStream;
 import java.io.DataOutput;
 import java.io.IOException;
 import java.nio.ByteBuffer;
@@ -33,7 +32,6 @@ import org.apache.cassandra.db.filter.QueryPath;
 import org.apache.cassandra.db.marshal.UUIDType;
 import org.apache.cassandra.io.IColumnSerializer;
 import org.apache.cassandra.io.IVersionedSerializer;
-import org.apache.cassandra.io.util.FastByteArrayInputStream;
 import org.apache.cassandra.net.MessageOut;
 import org.apache.cassandra.net.MessagingService;
 import org.apache.cassandra.thrift.ColumnOrSuperColumn;
@@ -53,8 +51,6 @@ public class RowMutation implements IMutation
 // map of column family id to mutations for that column family.
 protected MapUUID, ColumnFamily modifications = new HashMapUUID, 
ColumnFamily();
 
-private final MapInteger, byte[] preserializedBuffers = new 
HashMapInteger, byte[]();
-
 public RowMutation(String table, ByteBuffer key)
 {
 this(table, key, new HashMapUUID, ColumnFamily());
@@ -116,7 +112,7 @@ public class RowMutation implements IMutation
 
 // serialize the hint with id and version as a composite column name
 QueryPath path = new QueryPath(SystemTable.HINTS_CF, null, 
HintedHandOffManager.comparator.decompose(hintId, 
MessagingService.current_version));
-rm.add(path, 
ByteBuffer.wrap(mutation.getSerializedBuffer(MessagingService.current_version)),
 System.currentTimeMillis(), ttl);
+rm.add(path, ByteBuffer.wrap(FBUtilities.serialize(mutation, 
serializer, MessagingService.current_version)), System.currentTimeMillis(), 
ttl);
 
 return rm;
 }
@@ -277,17 +273,6 @@ public class RowMutation implements IMutation
 return new MessageOutRowMutation(verb, this, serializer);
 }
 
-public synchronized byte[] getSerializedBuffer(int version) throws 
IOException
-{
-byte[] bytes = preserializedBuffers.get(version);
-if (bytes == null)
-{
-bytes = FBUtilities.serialize(this, serializer, version);
-preserializedBuffers.put(version, bytes);
-}
-return bytes;
-}
-
 public String toString()
 {
 return toString(false);
@@ -358,25 +343,6 @@ public class RowMutation implements IMutation
 }
 }
 
-public static RowMutation fromBytes(byte[] raw, int version) throws 
IOException
-{
-RowMutation rm = serializer.deserialize(new DataInputStream(new 
FastByteArrayInputStream(raw)), version);
-boolean hasCounters = false;
-for (Map.EntryUUID, ColumnFamily entry : rm.modifications.entrySet())
-{
-if 
(entry.getValue().metadata().getDefaultValidator().isCommutative())
-{
-hasCounters = true;
-break;
-}
-}
-
-// We need to deserialize at least once for counters to cleanup the 
delta
-

[3/7] git commit: merge from 1.2

merge from 1.2


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/1dcf18ca
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/1dcf18ca
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/1dcf18ca

Branch: refs/heads/trunk
Commit: 1dcf18caa343fa1086482f5b1dfbbb00d2498d1c
Parents: d216b0d 1c79426
Author: Jonathan Ellis jbel...@apache.org
Authored: Tue Feb 5 15:41:52 2013 +0100
Committer: Jonathan Ellis jbel...@apache.org
Committed: Tue Feb 5 15:41:52 2013 +0100

--
 CHANGES.txt|1 +
 src/java/org/apache/cassandra/db/RowMutation.java  |   36 +--
 .../cassandra/db/commitlog/CommitLogSegment.java   |3 +-
 3 files changed, 4 insertions(+), 36 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/1dcf18ca/CHANGES.txt
--
diff --cc CHANGES.txt
index c282047,5e661ae..bf95ae1
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,11 -1,5 +1,12 @@@
 +1.3
 + * make index_interval configurable per columnfamily (CASSANDRA-3961)
 + * add default_tim_to_live (CASSANDRA-3974)
 + * add memtable_flush_period_in_ms (CASSANDRA-4237)
 + * replace supercolumns internally by composites (CASSANDRA-3237, 5123)
 + * upgrade thrift to 0.9.0 (CASSANDRA-3719)
 +
  1.2.2
+  * avoid no-op caching of byte[] on commitlog append (CASSANDRA-5199)
   * more robust solution to incomplete compactions + counters (CASSANDRA-5151)
   * fix symlinks under data dir not working (CASSANDRA-5185)
   * fix bug in compact storage metadata handling (CASSANDRA-5189)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/1dcf18ca/src/java/org/apache/cassandra/db/RowMutation.java
--
diff --cc src/java/org/apache/cassandra/db/RowMutation.java
index 7ad3100,5064c65..0fc4da8
--- a/src/java/org/apache/cassandra/db/RowMutation.java
+++ b/src/java/org/apache/cassandra/db/RowMutation.java
@@@ -29,9 -28,10 +28,8 @@@ import org.apache.commons.lang.StringUt
  import org.apache.cassandra.config.CFMetaData;
  import org.apache.cassandra.config.KSMetaData;
  import org.apache.cassandra.config.Schema;
 -import org.apache.cassandra.db.filter.QueryPath;
  import org.apache.cassandra.db.marshal.UUIDType;
 -import org.apache.cassandra.io.IColumnSerializer;
  import org.apache.cassandra.io.IVersionedSerializer;
- import org.apache.cassandra.io.util.FastByteArrayInputStream;
  import org.apache.cassandra.net.MessageOut;
  import org.apache.cassandra.net.MessagingService;
  import org.apache.cassandra.thrift.ColumnOrSuperColumn;
@@@ -113,9 -111,8 +109,9 @@@ public class RowMutation implements IMu
  ttl = Math.min(ttl, cf.metadata().getGcGraceSeconds());
  
  // serialize the hint with id and version as a composite column name
 -QueryPath path = new QueryPath(SystemTable.HINTS_CF, null, 
HintedHandOffManager.comparator.decompose(hintId, 
MessagingService.current_version));
 -rm.add(path, ByteBuffer.wrap(FBUtilities.serialize(mutation, 
serializer, MessagingService.current_version)), System.currentTimeMillis(), 
ttl);
 +ByteBuffer name = HintedHandOffManager.comparator.decompose(hintId, 
MessagingService.current_version);
- ByteBuffer value = 
ByteBuffer.wrap(mutation.getSerializedBuffer(MessagingService.current_version));
++ByteBuffer value = ByteBuffer.wrap(FBUtilities.serialize(mutation, 
serializer, MessagingService.current_version));
 +rm.add(SystemTable.HINTS_CF, name, value, System.currentTimeMillis(), 
ttl);
  
  return rm;
  }
@@@ -269,26 -299,50 +254,7 @@@
  return buff.append(])).toString();
  }
  
 -public void addColumnOrSuperColumn(String cfName, ColumnOrSuperColumn 
cosc)
 -{
 -if (cosc.super_column != null)
 -{
 -for (org.apache.cassandra.thrift.Column column : 
cosc.super_column.columns)
 -{
 -add(new QueryPath(cfName, cosc.super_column.name, 
column.name), column.value, column.timestamp, column.ttl);
 -}
 -}
 -else if (cosc.column != null)
 -{
 -add(new QueryPath(cfName, null, cosc.column.name), 
cosc.column.value, cosc.column.timestamp, cosc.column.ttl);
 -}
 -else if (cosc.counter_super_column != null)
 -{
 -for (org.apache.cassandra.thrift.CounterColumn column : 
cosc.counter_super_column.columns)
 -{
 -addCounter(new QueryPath(cfName, 
cosc.counter_super_column.name, column.name), column.value);
 -}
 -}
 -else // cosc.counter_column != null
 -{
 -addCounter(new QueryPath(cfName, null, cosc.counter_column.name),

[4/7] git commit: whitespace

whitespace


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/295d6af4
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/295d6af4
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/295d6af4

Branch: refs/heads/cassandra-1.2
Commit: 295d6af46d70e2eb84d655114c7bd1f430759ce4
Parents: 1c79426
Author: Jonathan Ellis jbel...@apache.org
Authored: Tue Feb 5 15:44:45 2013 +0100
Committer: Jonathan Ellis jbel...@apache.org
Committed: Tue Feb 5 15:44:45 2013 +0100

--
 CHANGES.txt |1 +
 1 files changed, 1 insertions(+), 0 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/295d6af4/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index 5e661ae..8e13b66 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -10,6 +10,7 @@
  * Make sstable directory picking blacklist-aware again (CASSANDRA-5193)
  * Correctly expire gossip states for edge cases (CASSANDRA-5216)
 
+
 1.2.1
  * stream undelivered hints on decommission (CASSANDRA-5128)
  * GossipingPropertyFileSnitch loads saved dc/rack info if needed 
(CASSANDRA-5133)

[7/7] git commit: Merge branch 'cassandra-1.2' into trunk

Updated Branches:
  refs/heads/cassandra-1.2 75d0f7a3f - 295d6af46
  refs/heads/trunk d216b0d28 - 7590b0267


Merge branch 'cassandra-1.2' into trunk


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/7590b026
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/7590b026
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/7590b026

Branch: refs/heads/trunk
Commit: 7590b0267714456b29b8f0de50dddf9be96f0bcb
Parents: baca0bc 295d6af
Author: Jonathan Ellis jbel...@apache.org
Authored: Tue Feb 5 15:45:55 2013 +0100
Committer: Jonathan Ellis jbel...@apache.org
Committed: Tue Feb 5 15:45:55 2013 +0100

--
 CHANGES.txt |1 +
 1 files changed, 1 insertions(+), 0 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/7590b026/CHANGES.txt
--

[1/7] git commit: avoid no-op caching of byte[] on commitlog append patch by jbellis; reviewed by yukim for CASSANDRA-5199

avoid no-op caching of byte[] on commitlog append
patch by jbellis; reviewed by yukim for CASSANDRA-5199


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/1c79426a
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/1c79426a
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/1c79426a

Branch: refs/heads/cassandra-1.2
Commit: 1c79426ab86a1d26e7214d8d86b8eb24d67c0ab0
Parents: 75d0f7a
Author: Jonathan Ellis jbel...@apache.org
Authored: Tue Feb 5 15:40:45 2013 +0100
Committer: Jonathan Ellis jbel...@apache.org
Committed: Tue Feb 5 15:40:45 2013 +0100

--
 CHANGES.txt|1 +
 src/java/org/apache/cassandra/db/RowMutation.java  |   36 +--
 .../cassandra/db/commitlog/CommitLogSegment.java   |3 +-
 3 files changed, 4 insertions(+), 36 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/1c79426a/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index e0e8079..5e661ae 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
 1.2.2
+ * avoid no-op caching of byte[] on commitlog append (CASSANDRA-5199)
  * more robust solution to incomplete compactions + counters (CASSANDRA-5151)
  * fix symlinks under data dir not working (CASSANDRA-5185)
  * fix bug in compact storage metadata handling (CASSANDRA-5189)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/1c79426a/src/java/org/apache/cassandra/db/RowMutation.java
--
diff --git a/src/java/org/apache/cassandra/db/RowMutation.java 
b/src/java/org/apache/cassandra/db/RowMutation.java
index a8e845d..5064c65 100644
--- a/src/java/org/apache/cassandra/db/RowMutation.java
+++ b/src/java/org/apache/cassandra/db/RowMutation.java
@@ -18,7 +18,6 @@
 package org.apache.cassandra.db;
 
 import java.io.DataInput;
-import java.io.DataInputStream;
 import java.io.DataOutput;
 import java.io.IOException;
 import java.nio.ByteBuffer;
@@ -33,7 +32,6 @@ import org.apache.cassandra.db.filter.QueryPath;
 import org.apache.cassandra.db.marshal.UUIDType;
 import org.apache.cassandra.io.IColumnSerializer;
 import org.apache.cassandra.io.IVersionedSerializer;
-import org.apache.cassandra.io.util.FastByteArrayInputStream;
 import org.apache.cassandra.net.MessageOut;
 import org.apache.cassandra.net.MessagingService;
 import org.apache.cassandra.thrift.ColumnOrSuperColumn;
@@ -53,8 +51,6 @@ public class RowMutation implements IMutation
 // map of column family id to mutations for that column family.
 protected MapUUID, ColumnFamily modifications = new HashMapUUID, 
ColumnFamily();
 
-private final MapInteger, byte[] preserializedBuffers = new 
HashMapInteger, byte[]();
-
 public RowMutation(String table, ByteBuffer key)
 {
 this(table, key, new HashMapUUID, ColumnFamily());
@@ -116,7 +112,7 @@ public class RowMutation implements IMutation
 
 // serialize the hint with id and version as a composite column name
 QueryPath path = new QueryPath(SystemTable.HINTS_CF, null, 
HintedHandOffManager.comparator.decompose(hintId, 
MessagingService.current_version));
-rm.add(path, 
ByteBuffer.wrap(mutation.getSerializedBuffer(MessagingService.current_version)),
 System.currentTimeMillis(), ttl);
+rm.add(path, ByteBuffer.wrap(FBUtilities.serialize(mutation, 
serializer, MessagingService.current_version)), System.currentTimeMillis(), 
ttl);
 
 return rm;
 }
@@ -277,17 +273,6 @@ public class RowMutation implements IMutation
 return new MessageOutRowMutation(verb, this, serializer);
 }
 
-public synchronized byte[] getSerializedBuffer(int version) throws 
IOException
-{
-byte[] bytes = preserializedBuffers.get(version);
-if (bytes == null)
-{
-bytes = FBUtilities.serialize(this, serializer, version);
-preserializedBuffers.put(version, bytes);
-}
-return bytes;
-}
-
 public String toString()
 {
 return toString(false);
@@ -358,25 +343,6 @@ public class RowMutation implements IMutation
 }
 }
 
-public static RowMutation fromBytes(byte[] raw, int version) throws 
IOException
-{
-RowMutation rm = serializer.deserialize(new DataInputStream(new 
FastByteArrayInputStream(raw)), version);
-boolean hasCounters = false;
-for (Map.EntryUUID, ColumnFamily entry : rm.modifications.entrySet())
-{
-if 
(entry.getValue().metadata().getDefaultValidator().isCommutative())
-{
-hasCounters = true;
-break;
-}
-}
-
-// We need to deserialize at least once for counters to cleanup the

[6/7] git commit: avoid serializing to byte[] on commitlog append patch by jbellis; reviewed by yukim for CASSANDRA-5199

avoid serializing to byte[] on commitlog append
patch by jbellis; reviewed by yukim for CASSANDRA-5199


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/baca0bc7
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/baca0bc7
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/baca0bc7

Branch: refs/heads/trunk
Commit: baca0bc7fe4b13bf8970f974c15d83701e02c048
Parents: 1dcf18c
Author: Jonathan Ellis jbel...@apache.org
Authored: Tue Feb 5 15:44:32 2013 +0100
Committer: Jonathan Ellis jbel...@apache.org
Committed: Tue Feb 5 15:45:34 2013 +0100

--
 CHANGES.txt|1 +
 .../cassandra/db/commitlog/CommitLogReplayer.java  |7 +++-
 .../cassandra/db/commitlog/CommitLogSegment.java   |   25 +++
 .../cassandra/io/util/ByteBufferOutputStream.java  |   25 ++
 .../cassandra/io/util/ChecksummedOutputStream.java |   35 +++
 .../org/apache/cassandra/utils/FBUtilities.java|9 
 6 files changed, 92 insertions(+), 10 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/baca0bc7/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index bf95ae1..b1c066c 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
 1.3
+ * avoid serializing to byte[] on commitlog append (CASSANDRA-5199)
  * make index_interval configurable per columnfamily (CASSANDRA-3961)
  * add default_tim_to_live (CASSANDRA-3974)
  * add memtable_flush_period_in_ms (CASSANDRA-4237)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/baca0bc7/src/java/org/apache/cassandra/db/commitlog/CommitLogReplayer.java
--
diff --git a/src/java/org/apache/cassandra/db/commitlog/CommitLogReplayer.java 
b/src/java/org/apache/cassandra/db/commitlog/CommitLogReplayer.java
index 705053b..107e9b7 100644
--- a/src/java/org/apache/cassandra/db/commitlog/CommitLogReplayer.java
+++ b/src/java/org/apache/cassandra/db/commitlog/CommitLogReplayer.java
@@ -167,9 +167,14 @@ public class CommitLogReplayer
 // This prevents CRC by being fooled by special-case 
garbage in the file; see CASSANDRA-2128
 if (serializedSize  10)
 break;
+
 long claimedSizeChecksum = reader.readLong();
 checksum.reset();
-checksum.update(serializedSize);
+if (CommitLogDescriptor.current_version  
CommitLogDescriptor.VERSION_20)
+checksum.update(serializedSize);
+else
+FBUtilities.updateChecksumInt(checksum, 
serializedSize);
+
 if (checksum.getValue() != claimedSizeChecksum)
 break; // entry wasn't synced correctly/fully. that's
// ok.

http://git-wip-us.apache.org/repos/asf/cassandra/blob/baca0bc7/src/java/org/apache/cassandra/db/commitlog/CommitLogSegment.java
--
diff --git a/src/java/org/apache/cassandra/db/commitlog/CommitLogSegment.java 
b/src/java/org/apache/cassandra/db/commitlog/CommitLogSegment.java
index 469ab99..9256214 100644
--- a/src/java/org/apache/cassandra/db/commitlog/CommitLogSegment.java
+++ b/src/java/org/apache/cassandra/db/commitlog/CommitLogSegment.java
@@ -17,6 +17,7 @@
  */
 package org.apache.cassandra.db.commitlog;
 
+import java.io.DataOutputStream;
 import java.io.File;
 import java.io.IOException;
 import java.io.RandomAccessFile;
@@ -38,6 +39,8 @@ import org.apache.cassandra.config.Schema;
 import org.apache.cassandra.db.ColumnFamily;
 import org.apache.cassandra.db.RowMutation;
 import org.apache.cassandra.io.FSWriteError;
+import org.apache.cassandra.io.util.ByteBufferOutputStream;
+import org.apache.cassandra.io.util.ChecksummedOutputStream;
 import org.apache.cassandra.io.util.FileUtils;
 import org.apache.cassandra.net.MessagingService;
 import org.apache.cassandra.utils.FBUtilities;
@@ -69,6 +72,8 @@ public class CommitLogSegment
 private boolean needsSync = false;
 
 private final MappedByteBuffer buffer;
+private final Checksum checksum;
+private final DataOutputStream bufferStream;
 private boolean closed;
 
 public final CommitLogDescriptor descriptor;
@@ -122,6 +127,8 @@ public class CommitLogSegment
 
logFileAccessor.setLength(DatabaseDescriptor.getCommitLogSegmentSize());
 
 buffer = 
logFileAccessor.getChannel().map(FileChannel.MapMode.READ_WRITE, 0, 
DatabaseDescriptor.getCommitLogSegmentSize());
+checksum = new PureJavaCrc32();
+bufferStream = new DataOutputStream(new

[5/7] git commit: whitespace

whitespace


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/295d6af4
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/295d6af4
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/295d6af4

Branch: refs/heads/trunk
Commit: 295d6af46d70e2eb84d655114c7bd1f430759ce4
Parents: 1c79426
Author: Jonathan Ellis jbel...@apache.org
Authored: Tue Feb 5 15:44:45 2013 +0100
Committer: Jonathan Ellis jbel...@apache.org
Committed: Tue Feb 5 15:44:45 2013 +0100

--
 CHANGES.txt |1 +
 1 files changed, 1 insertions(+), 0 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/295d6af4/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index 5e661ae..8e13b66 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -10,6 +10,7 @@
  * Make sstable directory picking blacklist-aware again (CASSANDRA-5193)
  * Correctly expire gossip states for edge cases (CASSANDRA-5216)
 
+
 1.2.1
  * stream undelivered hints on decommission (CASSANDRA-5128)
  * GossipingPropertyFileSnitch loads saved dc/rack info if needed 
(CASSANDRA-5133)

[jira] [Commented] (CASSANDRA-5222) OOM Exception during repair session with LeveledCompactionStrategy

2013-02-05 Thread Illarion Kovalchuk (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571370#comment-13571370
 ] 

Illarion Kovalchuk commented on CASSANDRA-5222:
---

It's quite possible that this quick fix will prevent repair to happen at all...

 OOM Exception during repair session with LeveledCompactionStrategy
 --

 Key: CASSANDRA-5222
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5222
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.0.0
 Environment: 3Gb Heap(12Gb per node RAM)
 36 nodes, 0.9 Tb of data per node, Leveled compaction strategy, SSTable size 
 =100Mb
Reporter: Ivan Sobolev
Assignee: Yuki Morishita
 Fix For: 1.1.10

 Attachments: chunks.json, sstablescanner.png


 1.8 Gb of heap is consumed with 12k SSTableBoundedScanner * 140kbytes

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Cassandra Wiki] Trivial Update of ClarkABN by ClarkABN

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The ClarkABN page has been changed by ClarkABN:
http://wiki.apache.org/cassandra/ClarkABN?action=diffrev1=1rev2=2

- Hey !! My name is SOFIA WALSH. I reside in McAllen. I am turning 32.BR
- I want to become a Navigator. I am a fan of matchboxes. My dad name is Chad  
and he is a Lifeguard. My mother is a Stuntman.BR
+ Yo bros !! My name is JACQULYN BROWNING. I live in Saginaw.BR
+ Soon i will turn 56. I want to become a Receptionist. One day i would want to 
do Video Games. My dad name is Douglas  and he is a Broker. My mummy is a 
Blacksmith.BR
  BR
- my web blog; [[http://michael-kors-shoes.blinkweb.com|michael kors outlet]]
+ Feel free to surf to my site ... 
[[http://michael-kors-shoes.blinkweb.com|michael kors watch]]

[jira] [Commented] (CASSANDRA-5222) OOM Exception during repair session with LeveledCompactionStrategy


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571411#comment-13571411
 ] 

Jonathan Ellis commented on CASSANDRA-5222:
---

Do you want it to not repair until your L0 is under control, or do you want it 
to think it can repair but then OOM when it tries? :)

Note: out-of-control L0 is a terrible long-term plan, if you can't keep L0 
mostly empty then you should just use STCS because really bad STCS is what 
LCS that can't keep up degrades to.

 OOM Exception during repair session with LeveledCompactionStrategy
 --

 Key: CASSANDRA-5222
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5222
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.0.0
 Environment: 3Gb Heap(12Gb per node RAM)
 36 nodes, 0.9 Tb of data per node, Leveled compaction strategy, SSTable size 
 =100Mb
Reporter: Ivan Sobolev
Assignee: Yuki Morishita
 Fix For: 1.1.10

 Attachments: chunks.json, sstablescanner.png


 1.8 Gb of heap is consumed with 12k SSTableBoundedScanner * 140kbytes

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-5222) OOM Exception during repair session with LeveledCompactionStrategy

2013-02-05 Thread Yuki Morishita (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571419#comment-13571419
 ] 

Yuki Morishita commented on CASSANDRA-5222:
---

This is not only for L0. Currently we are opening SSTBS for all sstable and 
then filter out those that are out of range. We can change that to only open 
the sstables for the range we are repairing. This change only still leaves the 
chance to OOM, so we can prevent repair to perform when the number of sstables 
for given range is too large.

 OOM Exception during repair session with LeveledCompactionStrategy
 --

 Key: CASSANDRA-5222
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5222
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.0.0
 Environment: 3Gb Heap(12Gb per node RAM)
 36 nodes, 0.9 Tb of data per node, Leveled compaction strategy, SSTable size 
 =100Mb
Reporter: Ivan Sobolev
Assignee: Yuki Morishita
 Fix For: 1.1.10

 Attachments: chunks.json, sstablescanner.png


 1.8 Gb of heap is consumed with 12k SSTableBoundedScanner * 140kbytes

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-5222) OOM Exception during repair session with LeveledCompactionStrategy


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571430#comment-13571430
 ] 

Jonathan Ellis commented on CASSANDRA-5222:
---

ValidationCompactionIterable does call cfs.getCompactionStrategy().getScanners 
which will use LeveledScanner for non-L0.

But I agree that there's no reason not to limit by range first.

 OOM Exception during repair session with LeveledCompactionStrategy
 --

 Key: CASSANDRA-5222
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5222
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.0.0
 Environment: 3Gb Heap(12Gb per node RAM)
 36 nodes, 0.9 Tb of data per node, Leveled compaction strategy, SSTable size 
 =100Mb
Reporter: Ivan Sobolev
Assignee: Yuki Morishita
 Fix For: 1.1.10

 Attachments: chunks.json, sstablescanner.png


 1.8 Gb of heap is consumed with 12k SSTableBoundedScanner * 140kbytes

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Cassandra Wiki] Trivial Update of KVVVeroni by KVVVeroni

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The KVVVeroni page has been changed by KVVVeroni:
http://wiki.apache.org/cassandra/KVVVeroni?action=diffrev1=2rev2=3

- Hey guys !! I am KARMA NEWTON. I work as a Coach.BR
- My daddy name is Bryan  and he is a Fowler. My mummy is a Guitarist.BR
+ Hello !! My name is LORAINE FRYE. I have a job as Military.BR
+ My father name is Shawn  and he is a Pathologist. My mummy is a 
Clergymen.BR
  BR
- Feel free to visit my website; 
[[http://www.unitedchem.com/beatbydre.aspx|monster earphones]]
+ Here is my website :: 
[[http://www.cleanscreenxcel.com/cheapmonsterbeatsbydre.html|monster earphones]]

[jira] [Commented] (CASSANDRA-5223) Secondary index doesn't get repaired

2013-02-05 Thread amorton (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571483#comment-13571483
 ] 

amorton commented on CASSANDRA-5223:


I tried running this but had to install the dtest package. I then got this when 
I ran it:

{noformat}
Traceback (most recent call last):
  File secondary_index_repair_test.py, line 1, in module
from dtest import Tester
  File 
/Users/aaron/code/scratch/CASSANDRA-5223/.env/lib/python2.7/site-packages/dtest/__init__.py,
 line 105, in module
from dtest.capture import Capturer
  File 
/Users/aaron/code/scratch/CASSANDRA-5223/.env/lib/python2.7/site-packages/dtest/capture.py,
 line 102, in module
from eventlet.corolocal import local
ImportError: No module named eventlet.corolocal
{noformat}

I'm also not sure where {{self.cluster}} is set. 

Can you remove all the unnecessary imports make it a simple script?


 Secondary index doesn't get repaired
 

 Key: CASSANDRA-5223
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5223
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.2.1
 Environment: Ubuntu dtest, laptop with 8G RAM
Reporter: Alexei Bakanov
 Attachments: secondary_index_repair_test.py


 Looks like secondary indexes don't get repaired by any of the Cassandra 
 repair mechanisms for NetworkTopologyStrategy. SimpleStrategy however works 
 fine.
 The issue started as a mail to Cassandra userlist: 
 http://article.gmane.org/gmane.comp.db.cassandra.user/30909
 I striped reproduction recipe down and made a d-test which inserts two rows 
 into a cluster of two nodes, where the first node goes down after the first 
 insert and goes back up after the second insert. Secondary index doesn't get 
 repaired by neither hinted-handoff, read repair, nor manual 'repair' 
 operation which the d-test triggers before reading the data.
 Moreover the second row is not visible in the index unless I do CL.ALL read 
 or drop/create the index.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Cassandra Wiki] Trivial Update of ShondaLu by ShondaLu

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The ShondaLu page has been changed by ShondaLu:
http://wiki.apache.org/cassandra/ShondaLu

New page:
Yo bros !! I am JETTA PEARSON. This spring iam going to be 24.BR
I study at The Practical Prep School in Palm Springs. I work as a Lifeguard. My 
father name is Chris  and he is a Captain. My momy is a Martial artist.BR
BR
Also visit my web blog; [[http://www.replica-chanelbagsol.com|chanel outlet]]

[Cassandra Wiki] Trivial Update of ShondaLu by ShondaLu

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The ShondaLu page has been changed by ShondaLu:
http://wiki.apache.org/cassandra/ShondaLu?action=diffrev1=1rev2=2

+ Wassp People !! I am LETTIE NICHOLS. I am turning 39.BR
- Yo bros !! I am JETTA PEARSON. This spring iam going to be 24.BR
- I study at The Practical Prep School in Palm Springs. I work as a Lifeguard. 
My father name is Chris  and he is a Captain. My momy is a Martial artist.BR
  BR
- Also visit my web blog; [[http://www.replica-chanelbagsol.com|chanel outlet]]
+ My parents want me to join The Interesting Prep School built at Canton. I 
have a job as Animal Trainer. My father name is Robert  and he is a Grocer. My 
mom is a Bricklayer.BR
+ BR
+ Here is my homepage ... [[http://www.chanelstorehandbags.com|chanel handbags]]

[Cassandra Wiki] Trivial Update of VerenaKci by VerenaKci

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The VerenaKci page has been changed by VerenaKci:
http://wiki.apache.org/cassandra/VerenaKci

New page:
Yo bros !! The name is BOK STEVENS. I am turning 28. I have applied for 
distance learning at The Jittery Institute built at Grand Prairie.BR
I am planning to become a Pianist. My father name is Douglas  and he is a 
Coach. My mother is a Fowler.BR
BR
Also visit my page ... [[http://www.replica-chanelbagsol.com|chanel outlet]]

[jira] [Created] (CASSANDRA-5224) alter table add in CQL3 allows adding columns to COMPACT STORAGE tables

2013-02-05 Thread Michael Kjellman (JIRA)

Michael Kjellman created CASSANDRA-5224:
---

 Summary: alter table add in CQL3 allows adding columns to COMPACT 
STORAGE tables
 Key: CASSANDRA-5224
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5224
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.2.1
Reporter: Michael Kjellman
Priority: Minor


From the docs:

These additions to a table are not allowed:

Adding a column having the same name as an existing column.
Adding columns to tables defined with COMPACT STORAGE.

however, this still works against a domain defined with COMPACT STORAGE in cqlsh

it appears that the metadata, however, is not defined correctly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-5223) Secondary index doesn't get repaired


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexei Bakanov updated CASSANDRA-5223:
--

Attachment: secondary_index_repair_test_2.py

removed unused imports

 Secondary index doesn't get repaired
 

 Key: CASSANDRA-5223
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5223
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.2.1
 Environment: Ubuntu dtest, laptop with 8G RAM
Reporter: Alexei Bakanov
 Attachments: secondary_index_repair_test_2.py, 
 secondary_index_repair_test.py


 Looks like secondary indexes don't get repaired by any of the Cassandra 
 repair mechanisms for NetworkTopologyStrategy. SimpleStrategy however works 
 fine.
 The issue started as a mail to Cassandra userlist: 
 http://article.gmane.org/gmane.comp.db.cassandra.user/30909
 I striped reproduction recipe down and made a d-test which inserts two rows 
 into a cluster of two nodes, where the first node goes down after the first 
 insert and goes back up after the second insert. Secondary index doesn't get 
 repaired by neither hinted-handoff, read repair, nor manual 'repair' 
 operation which the d-test triggers before reading the data.
 Moreover the second row is not visible in the index unless I do CL.ALL read 
 or drop/create the index.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-5221) NPE while upgrading from 1.1 to 1.2


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571533#comment-13571533
 ] 

Brandon Williams commented on CASSANDRA-5221:
-

The second problem looks like CASSANDRA-5107, though that was happening without 
upgrades.

 NPE while upgrading from 1.1 to 1.2
 ---

 Key: CASSANDRA-5221
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5221
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.2.1
Reporter: Vijay

 ERROR 00:29:25,208 Exception encountered during startup
 java.lang.NullPointerException
   at 
 org.apache.cassandra.db.SystemTable.upgradeSystemData(SystemTable.java:161)
   at 
 org.apache.cassandra.db.SystemTable.finishStartup(SystemTable.java:107)
   at 
 org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:276)
   at 
 org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:370)
   at 
 org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:413)
 java.lang.NullPointerException
   at 
 org.apache.cassandra.db.SystemTable.upgradeSystemData(SystemTable.java:161)
   at 
 org.apache.cassandra.db.SystemTable.finishStartup(SystemTable.java:107)
   at 
 org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:276)
   at 
 org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:370)
   at 
 org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:413)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CASSANDRA-5224) alter table add in CQL3 allows adding columns to COMPACT STORAGE tables


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brandon Williams reassigned CASSANDRA-5224:
---

Assignee: Aleksey Yeschenko

 alter table add in CQL3 allows adding columns to COMPACT STORAGE tables
 ---

 Key: CASSANDRA-5224
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5224
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.2.1
Reporter: Michael Kjellman
Assignee: Aleksey Yeschenko
Priority: Minor

 From the docs:
 These additions to a table are not allowed:
 Adding a column having the same name as an existing column.
 Adding columns to tables defined with COMPACT STORAGE.
 however, this still works against a domain defined with COMPACT STORAGE in 
 cqlsh
 it appears that the metadata, however, is not defined correctly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-5224) alter table add in CQL3 allows adding columns to COMPACT STORAGE tables


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brandon Williams updated CASSANDRA-5224:


Fix Version/s: 1.2.2

 alter table add in CQL3 allows adding columns to COMPACT STORAGE tables
 ---

 Key: CASSANDRA-5224
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5224
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.2.1
Reporter: Michael Kjellman
Assignee: Aleksey Yeschenko
Priority: Minor
 Fix For: 1.2.2


 From the docs:
 These additions to a table are not allowed:
 Adding a column having the same name as an existing column.
 Adding columns to tables defined with COMPACT STORAGE.
 however, this still works against a domain defined with COMPACT STORAGE in 
 cqlsh
 it appears that the metadata, however, is not defined correctly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Cassandra Wiki] Trivial Update of WilmaChon by WilmaChon

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The WilmaChon page has been changed by WilmaChon:
http://wiki.apache.org/cassandra/WilmaChon

New page:
Yo bros !! The name is ARGELIA KIM. I live in Omaha.BR
I might join The Cloudy Boarding School built at Naples. I am working as 
Navigator. My hobby is matchboxes. My father name is Cullen  and he is a Fire 
officer. My mom is a Governor.BR
BR
Also visit my webpage: [[http://discount-louis-vuitton.blinkweb.com|louis 
vuitton sale]]

[Cassandra Wiki] Trivial Update of Adrian608 by Adrian608

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The Adrian608 page has been changed by Adrian608:
http://wiki.apache.org/cassandra/Adrian608

New page:
Got nothing to say about me at all.BR
Hurrey Im here and a member of apache.org.BR
I just hope Im useful at allBR
BR
my web site ... [[http://investasiemas.pajajarancamp.com/|Investasi Emas]]

[2/3] git commit: add dsnitch comments

2013-02-05 Thread brandonwilliams

add dsnitch comments


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/acc3c8de
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/acc3c8de
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/acc3c8de

Branch: refs/heads/trunk
Commit: acc3c8de29b4d8826e45fc5dd956a67205a0b369
Parents: 295d6af
Author: Brandon Williams brandonwilli...@apache.org
Authored: Tue Feb 5 13:50:59 2013 -0600
Committer: Brandon Williams brandonwilli...@apache.org
Committed: Tue Feb 5 13:50:59 2013 -0600

--
 .../cassandra/locator/DynamicEndpointSnitch.java   |7 +++
 1 files changed, 7 insertions(+), 0 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/acc3c8de/src/java/org/apache/cassandra/locator/DynamicEndpointSnitch.java
--
diff --git a/src/java/org/apache/cassandra/locator/DynamicEndpointSnitch.java 
b/src/java/org/apache/cassandra/locator/DynamicEndpointSnitch.java
index 40aad20..214208e 100644
--- a/src/java/org/apache/cassandra/locator/DynamicEndpointSnitch.java
+++ b/src/java/org/apache/cassandra/locator/DynamicEndpointSnitch.java
@@ -230,6 +230,8 @@ public class DynamicEndpointSnitch extends 
AbstractEndpointSnitch implements ILa
 double maxLatency = 1;
 long maxPenalty = 1;
 HashMapInetAddress, Long penalties = new HashMapInetAddress, 
Long();
+// We're going to weight the latency and time since last reply for 
each host against the worst one we see, to arrive at sort of a 'badness 
percentage' for both of them.
+// first, find the worst for each.
 for (Map.EntryInetAddress, ExponentiallyDecayingSample entry : 
samples.entrySet())
 {
 double mean = entry.getValue().getSnapshot().getMedian();
@@ -238,18 +240,23 @@ public class DynamicEndpointSnitch extends 
AbstractEndpointSnitch implements ILa
 long timePenalty = lastReceived.containsKey(entry.getKey()) ? 
lastReceived.get(entry.getKey()) : System.currentTimeMillis();
 timePenalty = System.currentTimeMillis() - timePenalty;
 timePenalty = timePenalty  UPDATE_INTERVAL_IN_MS ? 
UPDATE_INTERVAL_IN_MS : timePenalty;
+// a convenient place to remember this since we've already 
calculated it and need it later
 penalties.put(entry.getKey(), timePenalty);
 if (timePenalty  maxPenalty)
 maxPenalty = timePenalty;
 }
+// now make another pass to do the weighting based on the maximums we 
found before
 for (Map.EntryInetAddress, ExponentiallyDecayingSample entry: 
samples.entrySet())
 {
 double score = entry.getValue().getSnapshot().getMedian() / 
maxLatency;
 if (penalties.containsKey(entry.getKey()))
 score += penalties.get(entry.getKey()) / ((double) maxPenalty);
 else
+// there's a chance a host was added to the samples after our 
previous loop to get the time penalties.  Add 1.0 to it, or '100% bad' for the 
time penalty.
 score += 1; // maxPenalty / maxPenalty
+// finally, add the severity without any weighting, since hosts 
scale this relative to their own load and the size of the task causing the 
severity
 score += StorageService.instance.getSeverity(entry.getKey());
+// lowest score (least amount of badness) wins.
 scores.put(entry.getKey(), score);
 }
 }

[1/3] git commit: add dsnitch comments

2013-02-05 Thread brandonwilliams

add dsnitch comments


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/acc3c8de
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/acc3c8de
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/acc3c8de

Branch: refs/heads/cassandra-1.2
Commit: acc3c8de29b4d8826e45fc5dd956a67205a0b369
Parents: 295d6af
Author: Brandon Williams brandonwilli...@apache.org
Authored: Tue Feb 5 13:50:59 2013 -0600
Committer: Brandon Williams brandonwilli...@apache.org
Committed: Tue Feb 5 13:50:59 2013 -0600

--
 .../cassandra/locator/DynamicEndpointSnitch.java   |7 +++
 1 files changed, 7 insertions(+), 0 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/acc3c8de/src/java/org/apache/cassandra/locator/DynamicEndpointSnitch.java
--
diff --git a/src/java/org/apache/cassandra/locator/DynamicEndpointSnitch.java 
b/src/java/org/apache/cassandra/locator/DynamicEndpointSnitch.java
index 40aad20..214208e 100644
--- a/src/java/org/apache/cassandra/locator/DynamicEndpointSnitch.java
+++ b/src/java/org/apache/cassandra/locator/DynamicEndpointSnitch.java
@@ -230,6 +230,8 @@ public class DynamicEndpointSnitch extends 
AbstractEndpointSnitch implements ILa
 double maxLatency = 1;
 long maxPenalty = 1;
 HashMapInetAddress, Long penalties = new HashMapInetAddress, 
Long();
+// We're going to weight the latency and time since last reply for 
each host against the worst one we see, to arrive at sort of a 'badness 
percentage' for both of them.
+// first, find the worst for each.
 for (Map.EntryInetAddress, ExponentiallyDecayingSample entry : 
samples.entrySet())
 {
 double mean = entry.getValue().getSnapshot().getMedian();
@@ -238,18 +240,23 @@ public class DynamicEndpointSnitch extends 
AbstractEndpointSnitch implements ILa
 long timePenalty = lastReceived.containsKey(entry.getKey()) ? 
lastReceived.get(entry.getKey()) : System.currentTimeMillis();
 timePenalty = System.currentTimeMillis() - timePenalty;
 timePenalty = timePenalty  UPDATE_INTERVAL_IN_MS ? 
UPDATE_INTERVAL_IN_MS : timePenalty;
+// a convenient place to remember this since we've already 
calculated it and need it later
 penalties.put(entry.getKey(), timePenalty);
 if (timePenalty  maxPenalty)
 maxPenalty = timePenalty;
 }
+// now make another pass to do the weighting based on the maximums we 
found before
 for (Map.EntryInetAddress, ExponentiallyDecayingSample entry: 
samples.entrySet())
 {
 double score = entry.getValue().getSnapshot().getMedian() / 
maxLatency;
 if (penalties.containsKey(entry.getKey()))
 score += penalties.get(entry.getKey()) / ((double) maxPenalty);
 else
+// there's a chance a host was added to the samples after our 
previous loop to get the time penalties.  Add 1.0 to it, or '100% bad' for the 
time penalty.
 score += 1; // maxPenalty / maxPenalty
+// finally, add the severity without any weighting, since hosts 
scale this relative to their own load and the size of the task causing the 
severity
 score += StorageService.instance.getSeverity(entry.getKey());
+// lowest score (least amount of badness) wins.
 scores.put(entry.getKey(), score);
 }
 }

[jira] [Updated] (CASSANDRA-4973) Secondary Index stops returning rows when caching=ALL


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-4973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexei Bakanov updated CASSANDRA-4973:
--

Attachment: secondary_index_rowcache_restart_test.py

I'm having the same issue and thought that it had something to do with 
datacenters (http://article.gmane.org/gmane.comp.db.cassandra.user/30935) But 
then I made a d-test in order to reproduce issue with CQL and found that it 
fails regardless of datacenter setup. Please find the d-test I made attached. 
It is quite random when it fails or passes, and I don't know why.

 Secondary Index stops returning rows when caching=ALL
 -

 Key: CASSANDRA-4973
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4973
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.2, 1.1.6
 Environment: Centos 6.3, Java 1.6.0_35, cass. 1.1.2 upgraded to 1.1.6
Reporter: Daniel Strawson
 Attachments: secondary_index_rowcache_restart_test.py


 I've been using cassandra on a project for a little while in development and 
 have recently suddenly started having an issue where the secondary index 
 stops working, this is happening on my new production system, we are not yet 
 live.   Things work ok one moment, then suddenly queries to the cf through 
 the secondary index stop returning data.  I've seen it happen on 3 CFs. I've 
 tried:
 - various nodetools repair / scrub / rebuild_indexes options, none seem to 
 make a difference.
 - Doing a 'update column family whatever with column_metadata=[]' then 
 repeating with my correct column_metadata definition.  This seems to fix the 
 problem (temporarily) until it comes back.
 The last time it happened I had just restarted cassandra, so it could be that 
 which is causing the issue, I've got the production system ok at the moment, 
 I will try restarting a bit later when its not being used and if I can get 
 the issue to reoccur I will add more information.
 The problem first manifested itself in 1.1.2, so I upgraded to 1.1.6, this 
 has not fixed it.
 Here is an example of the create column family I'm using for one of the CFs 
 that affected:
 create column family region
   with column_type = 'Standard'
   and comparator = 'UTF8Type'
   and default_validation_class = 'BytesType'
   and key_validation_class = 'UTF8Type'
   and read_repair_chance = 0.1
   and dclocal_read_repair_chance = 0.0
   and gc_grace = 864000
   and min_compaction_threshold = 4
   and max_compaction_threshold = 32
   and replicate_on_write = true
   and compaction_strategy = 
 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy'
   and caching = 'KEYS_ONLY'
   and column_metadata = [
 
 {column_name : 'label',
 validation_class : UTF8Type},
 
 {column_name : 'countryCode',
 validation_class : UTF8Type,
 index_name : 'region_countryCode_idx',
 index_type : 0},
 
 ]
   and compression_options = {'sstable_compression' : 
 'org.apache.cassandra.io.compress.SnappyCompressor'};
 I've noticed that CASSANDRA-4785 looks similar, in my case once the system 
 has the problem, it doesn't go away until I fix it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Comment Edited] (CASSANDRA-4973) Secondary Index stops returning rows when caching=ALL


[ 
https://issues.apache.org/jira/browse/CASSANDRA-4973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571669#comment-13571669
 ] 

Alexei Bakanov edited comment on CASSANDRA-4973 at 2/5/13 7:55 PM:
---

I'm having the same issue and thought that it had something to do with 
datacenters (http://article.gmane.org/gmane.comp.db.cassandra.user/30935) But 
then I made a d-test in order to reproduce issue with CQL so I could run 
TRACING I found that it fails regardless of datacenter setup. Please find the 
d-test I made attached. It is quite random when it fails or passes, and I don't 
know why.

  was (Author: alexeibakanov):
I'm having the same issue and thought that it had something to do with 
datacenters (http://article.gmane.org/gmane.comp.db.cassandra.user/30935) But 
then I made a d-test in order to reproduce issue with CQL so I can run TRACING 
I found that it fails regardless of datacenter setup. Please find the d-test I 
made attached. It is quite random when it fails or passes, and I don't know why.
  
 Secondary Index stops returning rows when caching=ALL
 -

 Key: CASSANDRA-4973
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4973
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.2, 1.1.6
 Environment: Centos 6.3, Java 1.6.0_35, cass. 1.1.2 upgraded to 1.1.6
Reporter: Daniel Strawson
 Attachments: secondary_index_rowcache_restart_test.py


 I've been using cassandra on a project for a little while in development and 
 have recently suddenly started having an issue where the secondary index 
 stops working, this is happening on my new production system, we are not yet 
 live.   Things work ok one moment, then suddenly queries to the cf through 
 the secondary index stop returning data.  I've seen it happen on 3 CFs. I've 
 tried:
 - various nodetools repair / scrub / rebuild_indexes options, none seem to 
 make a difference.
 - Doing a 'update column family whatever with column_metadata=[]' then 
 repeating with my correct column_metadata definition.  This seems to fix the 
 problem (temporarily) until it comes back.
 The last time it happened I had just restarted cassandra, so it could be that 
 which is causing the issue, I've got the production system ok at the moment, 
 I will try restarting a bit later when its not being used and if I can get 
 the issue to reoccur I will add more information.
 The problem first manifested itself in 1.1.2, so I upgraded to 1.1.6, this 
 has not fixed it.
 Here is an example of the create column family I'm using for one of the CFs 
 that affected:
 create column family region
   with column_type = 'Standard'
   and comparator = 'UTF8Type'
   and default_validation_class = 'BytesType'
   and key_validation_class = 'UTF8Type'
   and read_repair_chance = 0.1
   and dclocal_read_repair_chance = 0.0
   and gc_grace = 864000
   and min_compaction_threshold = 4
   and max_compaction_threshold = 32
   and replicate_on_write = true
   and compaction_strategy = 
 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy'
   and caching = 'KEYS_ONLY'
   and column_metadata = [
 
 {column_name : 'label',
 validation_class : UTF8Type},
 
 {column_name : 'countryCode',
 validation_class : UTF8Type,
 index_name : 'region_countryCode_idx',
 index_type : 0},
 
 ]
   and compression_options = {'sstable_compression' : 
 'org.apache.cassandra.io.compress.SnappyCompressor'};
 I've noticed that CASSANDRA-4785 looks similar, in my case once the system 
 has the problem, it doesn't go away until I fix it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Comment Edited] (CASSANDRA-4973) Secondary Index stops returning rows when caching=ALL


[ 
https://issues.apache.org/jira/browse/CASSANDRA-4973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571669#comment-13571669
 ] 

Alexei Bakanov edited comment on CASSANDRA-4973 at 2/5/13 7:54 PM:
---

I'm having the same issue and thought that it had something to do with 
datacenters (http://article.gmane.org/gmane.comp.db.cassandra.user/30935) But 
then I made a d-test in order to reproduce issue with CQL so I can run TRACING 
I found that it fails regardless of datacenter setup. Please find the d-test I 
made attached. It is quite random when it fails or passes, and I don't know why.

  was (Author: alexeibakanov):
I'm having the same issue and thought that it had something to do with 
datacenters (http://article.gmane.org/gmane.comp.db.cassandra.user/30935) But 
then I made a d-test in order to reproduce issue with CQL and found that it 
fails regardless of datacenter setup. Please find the d-test I made attached. 
It is quite random when it fails or passes, and I don't know why.
  
 Secondary Index stops returning rows when caching=ALL
 -

 Key: CASSANDRA-4973
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4973
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.2, 1.1.6
 Environment: Centos 6.3, Java 1.6.0_35, cass. 1.1.2 upgraded to 1.1.6
Reporter: Daniel Strawson
 Attachments: secondary_index_rowcache_restart_test.py


 I've been using cassandra on a project for a little while in development and 
 have recently suddenly started having an issue where the secondary index 
 stops working, this is happening on my new production system, we are not yet 
 live.   Things work ok one moment, then suddenly queries to the cf through 
 the secondary index stop returning data.  I've seen it happen on 3 CFs. I've 
 tried:
 - various nodetools repair / scrub / rebuild_indexes options, none seem to 
 make a difference.
 - Doing a 'update column family whatever with column_metadata=[]' then 
 repeating with my correct column_metadata definition.  This seems to fix the 
 problem (temporarily) until it comes back.
 The last time it happened I had just restarted cassandra, so it could be that 
 which is causing the issue, I've got the production system ok at the moment, 
 I will try restarting a bit later when its not being used and if I can get 
 the issue to reoccur I will add more information.
 The problem first manifested itself in 1.1.2, so I upgraded to 1.1.6, this 
 has not fixed it.
 Here is an example of the create column family I'm using for one of the CFs 
 that affected:
 create column family region
   with column_type = 'Standard'
   and comparator = 'UTF8Type'
   and default_validation_class = 'BytesType'
   and key_validation_class = 'UTF8Type'
   and read_repair_chance = 0.1
   and dclocal_read_repair_chance = 0.0
   and gc_grace = 864000
   and min_compaction_threshold = 4
   and max_compaction_threshold = 32
   and replicate_on_write = true
   and compaction_strategy = 
 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy'
   and caching = 'KEYS_ONLY'
   and column_metadata = [
 
 {column_name : 'label',
 validation_class : UTF8Type},
 
 {column_name : 'countryCode',
 validation_class : UTF8Type,
 index_name : 'region_countryCode_idx',
 index_type : 0},
 
 ]
   and compression_options = {'sstable_compression' : 
 'org.apache.cassandra.io.compress.SnappyCompressor'};
 I've noticed that CASSANDRA-4785 looks similar, in my case once the system 
 has the problem, it doesn't go away until I fix it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Reopened] (CASSANDRA-5196) IllegalStateException thrown when running new installation with old data directories


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Yeschenko reopened CASSANDRA-5196:
--


 IllegalStateException thrown when running new installation with old data 
 directories
 

 Key: CASSANDRA-5196
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5196
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.2.1
 Environment: CentOS 5.5
Reporter: Robbie Strickland
Assignee: Aleksey Yeschenko
Priority: Minor

 If you install 1.2.1 when there are existing data directories, the scrub 
 operation fails, throwing this exception:
 ERROR [main] 2013-01-29 15:05:06,564 FileUtils.java (line 373) Stopping the 
 gossiper and the RPC server
 ERROR [main] 2013-01-29 15:05:06,564 CassandraDaemon.java (line 387) 
 Exception encountered during startup
 java.lang.IllegalStateException: No configured daemon
   at 
 org.apache.cassandra.service.StorageService.stopRPCServer(StorageService.java:314)
   at 
 org.apache.cassandra.io.util.FileUtils.handleFSError(FileUtils.java:375)
   at org.apache.cassandra.db.Directories.init(Directories.java:113)
   at org.apache.cassandra.db.Directories.create(Directories.java:91)
   at 
 org.apache.cassandra.db.ColumnFamilyStore.scrubDataDirectories(ColumnFamilyStore.java:403)
   at 
 org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:174)
   at 
 org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:370)
   at 
 org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:413)
 This condition should produce a more reasonable exception.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-5196) IllegalStateException thrown when running new installation with old data directories


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Yeschenko updated CASSANDRA-5196:
-

Reviewer: brandon.williams

 IllegalStateException thrown when running new installation with old data 
 directories
 

 Key: CASSANDRA-5196
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5196
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.2.1
 Environment: CentOS 5.5
Reporter: Robbie Strickland
Assignee: Aleksey Yeschenko
Priority: Minor

 If you install 1.2.1 when there are existing data directories, the scrub 
 operation fails, throwing this exception:
 ERROR [main] 2013-01-29 15:05:06,564 FileUtils.java (line 373) Stopping the 
 gossiper and the RPC server
 ERROR [main] 2013-01-29 15:05:06,564 CassandraDaemon.java (line 387) 
 Exception encountered during startup
 java.lang.IllegalStateException: No configured daemon
   at 
 org.apache.cassandra.service.StorageService.stopRPCServer(StorageService.java:314)
   at 
 org.apache.cassandra.io.util.FileUtils.handleFSError(FileUtils.java:375)
   at org.apache.cassandra.db.Directories.init(Directories.java:113)
   at org.apache.cassandra.db.Directories.create(Directories.java:91)
   at 
 org.apache.cassandra.db.ColumnFamilyStore.scrubDataDirectories(ColumnFamilyStore.java:403)
   at 
 org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:174)
   at 
 org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:370)
   at 
 org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:413)
 This condition should produce a more reasonable exception.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-5196) IllegalStateException thrown when running new installation with old data directories


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Yeschenko updated CASSANDRA-5196:
-

Attachment: 5196.txt

 IllegalStateException thrown when running new installation with old data 
 directories
 

 Key: CASSANDRA-5196
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5196
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.2.1
 Environment: CentOS 5.5
Reporter: Robbie Strickland
Assignee: Aleksey Yeschenko
Priority: Minor
 Attachments: 5196.txt


 If you install 1.2.1 when there are existing data directories, the scrub 
 operation fails, throwing this exception:
 ERROR [main] 2013-01-29 15:05:06,564 FileUtils.java (line 373) Stopping the 
 gossiper and the RPC server
 ERROR [main] 2013-01-29 15:05:06,564 CassandraDaemon.java (line 387) 
 Exception encountered during startup
 java.lang.IllegalStateException: No configured daemon
   at 
 org.apache.cassandra.service.StorageService.stopRPCServer(StorageService.java:314)
   at 
 org.apache.cassandra.io.util.FileUtils.handleFSError(FileUtils.java:375)
   at org.apache.cassandra.db.Directories.init(Directories.java:113)
   at org.apache.cassandra.db.Directories.create(Directories.java:91)
   at 
 org.apache.cassandra.db.ColumnFamilyStore.scrubDataDirectories(ColumnFamilyStore.java:403)
   at 
 org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:174)
   at 
 org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:370)
   at 
 org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:413)
 This condition should produce a more reasonable exception.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-5196) IllegalStateException thrown when running new installation with old data directories


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Yeschenko updated CASSANDRA-5196:
-

Fix Version/s: 1.2.2

 IllegalStateException thrown when running new installation with old data 
 directories
 

 Key: CASSANDRA-5196
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5196
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.2.1
 Environment: CentOS 5.5
Reporter: Robbie Strickland
Assignee: Aleksey Yeschenko
Priority: Minor
 Fix For: 1.2.2

 Attachments: 5196.txt


 If you install 1.2.1 when there are existing data directories, the scrub 
 operation fails, throwing this exception:
 ERROR [main] 2013-01-29 15:05:06,564 FileUtils.java (line 373) Stopping the 
 gossiper and the RPC server
 ERROR [main] 2013-01-29 15:05:06,564 CassandraDaemon.java (line 387) 
 Exception encountered during startup
 java.lang.IllegalStateException: No configured daemon
   at 
 org.apache.cassandra.service.StorageService.stopRPCServer(StorageService.java:314)
   at 
 org.apache.cassandra.io.util.FileUtils.handleFSError(FileUtils.java:375)
   at org.apache.cassandra.db.Directories.init(Directories.java:113)
   at org.apache.cassandra.db.Directories.create(Directories.java:91)
   at 
 org.apache.cassandra.db.ColumnFamilyStore.scrubDataDirectories(ColumnFamilyStore.java:403)
   at 
 org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:174)
   at 
 org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:370)
   at 
 org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:413)
 This condition should produce a more reasonable exception.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Cassandra Wiki] Trivial Update of LesterBro by LesterBro

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The LesterBro page has been changed by LesterBro:
http://wiki.apache.org/cassandra/LesterBro

New page:
My name: Helaine GomesBR
Age: 18BR
Country: AustraliaBR
City: Macleay Island BR
Post code: 4184BR
Street: 35 Shirley StreetBR
BR
Here is my blog [[http://louis-vuitton-outlets.blinkweb.com|louis vuitton 
wallets]]

[Cassandra Wiki] Trivial Update of Roscoe21U by Roscoe21U

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The Roscoe21U page has been changed by Roscoe21U:
http://wiki.apache.org/cassandra/Roscoe21U

New page:
I have a house in Syracuse. Soon i will turn 25. I have applied for distance 
learning at The Instructive Boarding School built at Appleton.BR
BR
I want to become a Importer. I like to do Cosplay. My papa name is Tom and he 
is a Construction worker. My momy is a Joiner.BR
BR
Feel free to visit my page [[http://www.unitedchem.com/beatbydre.aspx|dr dre 
beats review]]

git commit: cqlsh tracing: ninja-remove quotes around session_id

2013-02-05 Thread aleksey

Updated Branches:
  refs/heads/cassandra-1.2 acc3c8de2 - ae3efc2d0


cqlsh tracing: ninja-remove quotes around session_id


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/ae3efc2d
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/ae3efc2d
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/ae3efc2d

Branch: refs/heads/cassandra-1.2
Commit: ae3efc2d069e0035938f47b69a43065ce2d69e60
Parents: acc3c8d
Author: Aleksey Yeschenko alek...@apache.org
Authored: Wed Feb 6 00:03:08 2013 +0300
Committer: Aleksey Yeschenko alek...@apache.org
Committed: Wed Feb 6 00:03:08 2013 +0300

--
 pylib/cqlshlib/tracing.py |4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/ae3efc2d/pylib/cqlshlib/tracing.py
--
diff --git a/pylib/cqlshlib/tracing.py b/pylib/cqlshlib/tracing.py
index 9cbea92..fb8525d 100644
--- a/pylib/cqlshlib/tracing.py
+++ b/pylib/cqlshlib/tracing.py
@@ -40,13 +40,13 @@ def print_trace_session(shell, cursor, session_id):
 def fetch_trace_session(cursor, session_id):
 cursor.execute(SELECT request, coordinator, started_at, duration 
FROM %s.%s 
-   WHERE session_id = '%s' % (TRACING_KS, SESSIONS_CF, 
session_id),
+   WHERE session_id = %s % (TRACING_KS, SESSIONS_CF, 
session_id),
consistency_level='ONE')
 (request, coordinator, started_at, duration) = cursor.fetchone()
 
 cursor.execute(SELECT activity, event_id, source, source_elapsed 
FROM %s.%s 
-   WHERE session_id = '%s' % (TRACING_KS, EVENTS_CF, 
session_id),
+   WHERE session_id = %s % (TRACING_KS, EVENTS_CF, 
session_id),
consistency_level='ONE')
 events = cursor.fetchall()

[2/2] git commit: Merge branch 'cassandra-1.2' into trunk

2013-02-05 Thread aleksey

Updated Branches:
  refs/heads/trunk 7ca99351e - 76bad8cec


Merge branch 'cassandra-1.2' into trunk


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/76bad8ce
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/76bad8ce
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/76bad8ce

Branch: refs/heads/trunk
Commit: 76bad8cec02151ede83aeb9800d5c37e169114d0
Parents: 7ca9935 ae3efc2
Author: Aleksey Yeschenko alek...@apache.org
Authored: Wed Feb 6 00:05:17 2013 +0300
Committer: Aleksey Yeschenko alek...@apache.org
Committed: Wed Feb 6 00:05:17 2013 +0300

--
 pylib/cqlshlib/tracing.py |4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)
--

[1/2] git commit: cqlsh tracing: ninja-remove quotes around session_id

2013-02-05 Thread aleksey

cqlsh tracing: ninja-remove quotes around session_id


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/ae3efc2d
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/ae3efc2d
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/ae3efc2d

Branch: refs/heads/trunk
Commit: ae3efc2d069e0035938f47b69a43065ce2d69e60
Parents: acc3c8d
Author: Aleksey Yeschenko alek...@apache.org
Authored: Wed Feb 6 00:03:08 2013 +0300
Committer: Aleksey Yeschenko alek...@apache.org
Committed: Wed Feb 6 00:03:08 2013 +0300

--
 pylib/cqlshlib/tracing.py |4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/ae3efc2d/pylib/cqlshlib/tracing.py
--
diff --git a/pylib/cqlshlib/tracing.py b/pylib/cqlshlib/tracing.py
index 9cbea92..fb8525d 100644
--- a/pylib/cqlshlib/tracing.py
+++ b/pylib/cqlshlib/tracing.py
@@ -40,13 +40,13 @@ def print_trace_session(shell, cursor, session_id):
 def fetch_trace_session(cursor, session_id):
 cursor.execute(SELECT request, coordinator, started_at, duration 
FROM %s.%s 
-   WHERE session_id = '%s' % (TRACING_KS, SESSIONS_CF, 
session_id),
+   WHERE session_id = %s % (TRACING_KS, SESSIONS_CF, 
session_id),
consistency_level='ONE')
 (request, coordinator, started_at, duration) = cursor.fetchone()
 
 cursor.execute(SELECT activity, event_id, source, source_elapsed 
FROM %s.%s 
-   WHERE session_id = '%s' % (TRACING_KS, EVENTS_CF, 
session_id),
+   WHERE session_id = %s % (TRACING_KS, EVENTS_CF, 
session_id),
consistency_level='ONE')
 events = cursor.fetchall()

[Cassandra Wiki] Trivial Update of Georgetta by Georgetta

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The Georgetta page has been changed by Georgetta:
http://wiki.apache.org/cassandra/Georgetta

New page:
Hello !! The name is ISABELLE WEBSTER. I am staying at Bakersfield.BR
I might join The Radical Boarding School situated in Leicester. I am self 
employed as a Mechanician. I like to do Dancing. My papa name is Willaim and he 
is a Analyst. My mom is a Explorer.BR
BR
Also visit my web blog ... 
[[http://discountlouisvuittonrespectonline.webs.com|lv handbags]]

[jira] [Commented] (CASSANDRA-5068) CLONE - Once a host has been hinted to, log messages for it repeat every 10 mins even if no hints are delivered


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571758#comment-13571758
 ] 

Brandon Williams commented on CASSANDRA-5068:
-

I ran into this in 1.2, and the problem is definitely old sstables full of 
tombstones being left behind:

{noformat}
 activity   
 | timestamp| source| source_elapsed
-+--+---+
  
execute_cql3_query | 21:10:25,847 | 10.179.64.227 |  0
   
Parsing statement | 21:10:25,847 | 10.179.64.227 | 39
  
Peparing statement | 21:10:25,847 | 10.179.64.227 |208
   Determining 
replicas to query | 21:10:25,847 | 10.179.64.227 |316
 Executing seq scan across 2 sstables for [min(-9223372036854775808), 
min(-9223372036854775808)] | 21:10:25,870 | 10.179.64.227 |  23223
  Read 0 live cells and 
13800 tombstoned | 21:10:25,928 | 10.179.64.227 |  81432
  Read 0 live cells and 
13068 tombstoned | 21:10:26,015 | 10.179.64.227 | 168213
Scanned 2 
rows and matched 2 | 21:10:26,016 | 10.179.64.227 | 169206

Request complete | 21:10:26,016 | 10.179.64.227 | 169585
{noformat}


The problem appears to occur here:

{noformat}
 INFO [GossipStage:1] 2013-02-04 22:54:34,828 Gossiper.java (line 754) 
InetAddress /10.179.111.137 is now UP
 INFO [GossipStage:1] 2013-02-04 22:54:34,830 Gossiper.java (line 754) 
InetAddress /10.179.65.102 is now UP
 INFO [HintedHandoff:1] 2013-02-04 22:54:34,830 HintedHandOffManager.java (line 
297) Started hinted handoff for host: 5b49c861-0cf6-48dc-872a-7fcb89429dae with 
IP: /10.179.111.137
 INFO [HintedHandoff:2] 2013-02-04 22:54:34,830 HintedHandOffManager.java (line 
297) Started hinted handoff for host: 0fd1d3b1-0f73-40fd-ab36-9f4b9636a205 with 
IP: /10.179.65.102
 INFO [HintedHandoff:2] 2013-02-04 22:54:41,039 ColumnFamilyStore.java (line 
678) Enqueuing flush of Memtable-hints@164677298(1020984/1020984 
serialized/live bytes, 39151 ops)
 INFO [FlushWriter:2] 2013-02-04 22:54:41,041 Memtable.java (line 453) Writing 
Memtable-hints@164677298(1020984/1020984 serialized/live bytes, 39151 ops)
 INFO [CompactionExecutor:8] 2013-02-04 22:54:41,043 CompactionTask.java (line 
112) Compacting 
[SSTableReader(path='/var/lib/cassandra/data/system/hints/system-hints-ib-1-Data.db')]
 INFO [FlushWriter:2] 2013-02-04 22:54:41,200 Memtable.java (line 487) 
Completed flushing 
/var/lib/cassandra/data/system/hints/system-hints-ib-2-Data.db (166760 bytes) 
for commitlog position ReplayPosition(segmentId=1360018215672, 
position=11404848)
 INFO [CompactionExecutor:9] 2013-02-04 22:54:41,215 CompactionManager.java 
(line 452) SSTables for user defined compaction are already being compacted.
 INFO [HintedHandoff:2] 2013-02-04 22:54:41,216 HintedHandOffManager.java (line 
412) Finished hinted handoff of 13909 rows to endpoint /10.179.65.102
 INFO [CompactionExecutor:8] 2013-02-04 22:54:41,444 CompactionTask.java (line 
272) Compacted 1 sstables to 
[/var/lib/cassandra/data/system/hints/system-hints-ib-3,].  625,567 bytes to 
625,567 (~100% of original) in 401ms = 1.487749MB/s.  2 total rows, 2 unique.  
Row merge counts were {1:2, }
 INFO [HintedHandoff:1] 2013-02-04 22:54:41,445 HintedHandOffManager.java (line 
412) Finished hinted handoff of 13230 rows to endpoint /10.179.111.137
{noformat}

The problem is that with concurrent delivery we end up in a state where we have 
two sstables that contain tombstones, each containing some portion of them for 
the endpoints that were delivered to.  Since we never replay any rows again, we 
never compact again, and thus never evict the tombstones.

I think I'm back to what I proposed before of just removing the replayed  0 
check and letting isEmpty check handle the common case.
 

 CLONE - Once a host has been hinted to, log messages for it repeat every 10 
 mins even if no hints are delivered
 ---

 Key: CASSANDRA-5068
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5068
 Project:

[Cassandra Wiki] Trivial Update of Georgetta by Georgetta

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The Georgetta page has been changed by Georgetta:
http://wiki.apache.org/cassandra/Georgetta?action=diffrev1=1rev2=2

- Hello !! The name is ISABELLE WEBSTER. I am staying at Bakersfield.BR
- I might join The Radical Boarding School situated in Leicester. I am self 
employed as a Mechanician. I like to do Dancing. My papa name is Willaim and he 
is a Analyst. My mom is a Explorer.BR
+ Hey !! The name is NICOLE GILLIAM. I am staying at Oxford.BR
+ I go to night school at The Weird School which has a branch in Scottsdale. I 
am planning to become a Author. I like YoYo. My papa name is Karl  and he is a 
Physiotherapist. My momy is a Childcare worker.BR
  BR
- Also visit my web blog ... 
[[http://discountlouisvuittonrespectonline.webs.com|lv handbags]]
+ My page [[http://discountlouisvuittonrespectonline.webs.com|cheap louis 
vuitton bags]]

[jira] [Updated] (CASSANDRA-5068) CLONE - Once a host has been hinted to, log messages for it repeat every 10 mins even if no hints are delivered


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brandon Williams updated CASSANDRA-5068:


Attachment: 5068.txt

 CLONE - Once a host has been hinted to, log messages for it repeat every 10 
 mins even if no hints are delivered
 ---

 Key: CASSANDRA-5068
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5068
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.6, 1.2.0
 Environment: cassandra 1.1.6
 java 1.6.0_30
Reporter: Peter Haggerty
Assignee: Brandon Williams
Priority: Minor
  Labels: hinted, hintedhandoff, phantom
 Attachments: 5068.txt


 We have 0 row hinted handoffs every 10 minutes like clockwork. This impacts 
 our ability to monitor the cluster by adding persistent noise in the handoff 
 metric.
 Previous mentions of this issue are here:
 http://www.mail-archive.com/user@cassandra.apache.org/msg25982.html
 The hinted handoffs can be scrubbed away with
 nodetool -h 127.0.0.1 scrub system HintsColumnFamily
 but they return after anywhere from a few minutes to multiple hours later.
 These started to appear after an upgrade to 1.1.6 and haven't gone away 
 despite rolling cleanups, rolling restarts, multiple rounds of scrubbing, etc.
 A few things we've noticed about the handoffs:
 1. The phantom handoff endpoint changes after a non-zero handoff comes through
 2. Sometimes a non-zero handoff will be immediately followed by an off 
 schedule phantom handoff to the endpoint the phantom had been using before
 3. The sstable2json output seems to include multiple sub-sections for each 
 handoff with the same deletedAt information.
 The phantom handoff endpoint changes after a non-zero handoff comes through:
  INFO [HintedHandoff:1] 2012-12-11 06:57:35,093 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.1
  INFO [HintedHandoff:1] 2012-12-11 07:07:35,092 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.1
  INFO [HintedHandoff:1] 2012-12-11 07:07:37,915 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 1058 rows to endpoint /10.10.10.2
  INFO [HintedHandoff:1] 2012-12-11 07:17:35,093 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.2
  INFO [HintedHandoff:1] 2012-12-11 07:27:35,093 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.2
 Sometimes a non-zero handoff will be immediately followed by an off 
 schedule phantom handoff to the endpoint the phantom had been using before:
  INFO [HintedHandoff:1] 2012-12-12 21:47:39,335 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.3
  INFO [HintedHandoff:1] 2012-12-12 21:57:39,335 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.3
  INFO [HintedHandoff:1] 2012-12-12 22:07:43,319 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 1416 rows to endpoint /10.10.10.4
  INFO [HintedHandoff:1] 2012-12-12 22:07:43,320 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.3
  INFO [HintedHandoff:1] 2012-12-12 22:17:39,357 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.4
  INFO [HintedHandoff:1] 2012-12-12 22:27:39,337 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.4
 The first few entries from one of the json files:
 {
 0aaa: {
 ccf5dc203a2211e2e154da71a9bb: {
 deletedAt: -9223372036854775808, 
 subColumns: []
 }, 
 ccf603303a2211e2e154da71a9bb: {
 deletedAt: -9223372036854775808, 
 subColumns: []
 }, 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-5068) CLONE - Once a host has been hinted to, log messages for it repeat every 10 mins even if no hints are delivered


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brandon Williams updated CASSANDRA-5068:


Labels: hinted hintedhandoff  (was: hinted hintedhandoff phantom)

 CLONE - Once a host has been hinted to, log messages for it repeat every 10 
 mins even if no hints are delivered
 ---

 Key: CASSANDRA-5068
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5068
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.6, 1.2.0
 Environment: cassandra 1.1.6
 java 1.6.0_30
Reporter: Peter Haggerty
Assignee: Brandon Williams
Priority: Minor
  Labels: hinted, hintedhandoff
 Attachments: 5068.txt


 We have 0 row hinted handoffs every 10 minutes like clockwork. This impacts 
 our ability to monitor the cluster by adding persistent noise in the handoff 
 metric.
 Previous mentions of this issue are here:
 http://www.mail-archive.com/user@cassandra.apache.org/msg25982.html
 The hinted handoffs can be scrubbed away with
 nodetool -h 127.0.0.1 scrub system HintsColumnFamily
 but they return after anywhere from a few minutes to multiple hours later.
 These started to appear after an upgrade to 1.1.6 and haven't gone away 
 despite rolling cleanups, rolling restarts, multiple rounds of scrubbing, etc.
 A few things we've noticed about the handoffs:
 1. The phantom handoff endpoint changes after a non-zero handoff comes through
 2. Sometimes a non-zero handoff will be immediately followed by an off 
 schedule phantom handoff to the endpoint the phantom had been using before
 3. The sstable2json output seems to include multiple sub-sections for each 
 handoff with the same deletedAt information.
 The phantom handoff endpoint changes after a non-zero handoff comes through:
  INFO [HintedHandoff:1] 2012-12-11 06:57:35,093 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.1
  INFO [HintedHandoff:1] 2012-12-11 07:07:35,092 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.1
  INFO [HintedHandoff:1] 2012-12-11 07:07:37,915 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 1058 rows to endpoint /10.10.10.2
  INFO [HintedHandoff:1] 2012-12-11 07:17:35,093 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.2
  INFO [HintedHandoff:1] 2012-12-11 07:27:35,093 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.2
 Sometimes a non-zero handoff will be immediately followed by an off 
 schedule phantom handoff to the endpoint the phantom had been using before:
  INFO [HintedHandoff:1] 2012-12-12 21:47:39,335 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.3
  INFO [HintedHandoff:1] 2012-12-12 21:57:39,335 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.3
  INFO [HintedHandoff:1] 2012-12-12 22:07:43,319 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 1416 rows to endpoint /10.10.10.4
  INFO [HintedHandoff:1] 2012-12-12 22:07:43,320 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.3
  INFO [HintedHandoff:1] 2012-12-12 22:17:39,357 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.4
  INFO [HintedHandoff:1] 2012-12-12 22:27:39,337 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.4
 The first few entries from one of the json files:
 {
 0aaa: {
 ccf5dc203a2211e2e154da71a9bb: {
 deletedAt: -9223372036854775808, 
 subColumns: []
 }, 
 ccf603303a2211e2e154da71a9bb: {
 deletedAt: -9223372036854775808, 
 subColumns: []
 }, 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Cassandra Wiki] Trivial Update of cheap_christian_louboutin_w3Z2 by Candelari

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The cheap_christian_louboutin_w3Z2 page has been changed by Candelari:
http://wiki.apache.org/cassandra/cheap_christian_louboutin_w3Z2

New page:
[[http://www.fairchanelstore.com|http://www.fairchanelstore.com]]BR
[[http://www.fairchanelstore.com|chanel handbags]]BR
[[http://www.fairchanelstore.com|chanel outlet]]BR
[[http://www.fairchanelstore.com|chanel bags]]BR
Xiao Chen and additionally perception blameful, icon can certainly from 
underwater dragon, is among the most terrible control of your coastal, 
day-to-day innumerable deal to material.BR
BR
Gleaming and additionally clear ovum ended up being as a final point destroyed, 
silver precious metal Guanghua remarkable. Egg vivid white leaped away, 
speedily in the rub, aided by the center in sterling silver Centimeter ovum 
yolk Inch, over the glory with Guanghua amount, is derived from the 
application.BR
BR
If the unknown free of very long Xiao, Xiao Chen released your radio stations, 
the person was in fact astounded to see a metallic dragon, for how long, it 
really is a significant dragon produce intimidating expressions, from your wild 
hair by having a quite strong everyday life change.BR
BR
This can be the fact of this Monster through!BR
BR
They're with no delay, which will routine silver Guanghua swallow. At that 
time, Xiao Chen emotion soul gave the impression to burn the reccommended, any 
floods electrical power for everyday life, within the figure towards severe 
impact!BR
BR
A intense ogre sit eggs, carries a particularly strong life vitality, of 
course, the forthcoming so that you can hatch some deep monster! Hereditary 
life part tremendously abounding.BR
BR
The gold Xiaguang round Cheng-Lun Hsiao system, just like typically the fires 
consuming generally, is it doesn't effusion for ovum includes, will be the 
never-ending everyday life jingyuan. His or her physique will become pretty 
much transparent, whenever in the event if perhaps when are able to access, an 
important components dragon sank in to the seaside in the.BR
[[http://www.shoesashlen.com|http://www.shoesashlen.com]]BR
[[http://www.shoesashlen.com|christian louboutin outlet]]BR
[[http://www.shoesashlen.com|christian louboutin sale]]BR
[[http://www.fairchanelstore.com|chanel replica]]

[jira] [Commented] (CASSANDRA-5068) CLONE - Once a host has been hinted to, log messages for it repeat every 10 mins even if no hints are delivered


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571769#comment-13571769
 ] 

Jonathan Ellis commented on CASSANDRA-5068:
---

Shouldn't the I have  X % tombstones in this sstable code kick in?

 CLONE - Once a host has been hinted to, log messages for it repeat every 10 
 mins even if no hints are delivered
 ---

 Key: CASSANDRA-5068
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5068
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.6, 1.2.0
 Environment: cassandra 1.1.6
 java 1.6.0_30
Reporter: Peter Haggerty
Assignee: Brandon Williams
Priority: Minor
  Labels: hinted, hintedhandoff
 Attachments: 5068.txt


 We have 0 row hinted handoffs every 10 minutes like clockwork. This impacts 
 our ability to monitor the cluster by adding persistent noise in the handoff 
 metric.
 Previous mentions of this issue are here:
 http://www.mail-archive.com/user@cassandra.apache.org/msg25982.html
 The hinted handoffs can be scrubbed away with
 nodetool -h 127.0.0.1 scrub system HintsColumnFamily
 but they return after anywhere from a few minutes to multiple hours later.
 These started to appear after an upgrade to 1.1.6 and haven't gone away 
 despite rolling cleanups, rolling restarts, multiple rounds of scrubbing, etc.
 A few things we've noticed about the handoffs:
 1. The phantom handoff endpoint changes after a non-zero handoff comes through
 2. Sometimes a non-zero handoff will be immediately followed by an off 
 schedule phantom handoff to the endpoint the phantom had been using before
 3. The sstable2json output seems to include multiple sub-sections for each 
 handoff with the same deletedAt information.
 The phantom handoff endpoint changes after a non-zero handoff comes through:
  INFO [HintedHandoff:1] 2012-12-11 06:57:35,093 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.1
  INFO [HintedHandoff:1] 2012-12-11 07:07:35,092 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.1
  INFO [HintedHandoff:1] 2012-12-11 07:07:37,915 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 1058 rows to endpoint /10.10.10.2
  INFO [HintedHandoff:1] 2012-12-11 07:17:35,093 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.2
  INFO [HintedHandoff:1] 2012-12-11 07:27:35,093 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.2
 Sometimes a non-zero handoff will be immediately followed by an off 
 schedule phantom handoff to the endpoint the phantom had been using before:
  INFO [HintedHandoff:1] 2012-12-12 21:47:39,335 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.3
  INFO [HintedHandoff:1] 2012-12-12 21:57:39,335 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.3
  INFO [HintedHandoff:1] 2012-12-12 22:07:43,319 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 1416 rows to endpoint /10.10.10.4
  INFO [HintedHandoff:1] 2012-12-12 22:07:43,320 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.3
  INFO [HintedHandoff:1] 2012-12-12 22:17:39,357 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.4
  INFO [HintedHandoff:1] 2012-12-12 22:27:39,337 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.4
 The first few entries from one of the json files:
 {
 0aaa: {
 ccf5dc203a2211e2e154da71a9bb: {
 deletedAt: -9223372036854775808, 
 subColumns: []
 }, 
 ccf603303a2211e2e154da71a9bb: {
 deletedAt: -9223372036854775808, 
 subColumns: []
 }, 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-5068) CLONE - Once a host has been hinted to, log messages for it repeat every 10 mins even if no hints are delivered

2013-02-05 Thread Peter Haggerty (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571772#comment-13571772
 ] 

Peter Haggerty commented on CASSANDRA-5068:
---

We see this in 1.1.9 as well.

 CLONE - Once a host has been hinted to, log messages for it repeat every 10 
 mins even if no hints are delivered
 ---

 Key: CASSANDRA-5068
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5068
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.6, 1.2.0
 Environment: cassandra 1.1.6
 java 1.6.0_30
Reporter: Peter Haggerty
Assignee: Brandon Williams
Priority: Minor
  Labels: hinted, hintedhandoff
 Attachments: 5068.txt


 We have 0 row hinted handoffs every 10 minutes like clockwork. This impacts 
 our ability to monitor the cluster by adding persistent noise in the handoff 
 metric.
 Previous mentions of this issue are here:
 http://www.mail-archive.com/user@cassandra.apache.org/msg25982.html
 The hinted handoffs can be scrubbed away with
 nodetool -h 127.0.0.1 scrub system HintsColumnFamily
 but they return after anywhere from a few minutes to multiple hours later.
 These started to appear after an upgrade to 1.1.6 and haven't gone away 
 despite rolling cleanups, rolling restarts, multiple rounds of scrubbing, etc.
 A few things we've noticed about the handoffs:
 1. The phantom handoff endpoint changes after a non-zero handoff comes through
 2. Sometimes a non-zero handoff will be immediately followed by an off 
 schedule phantom handoff to the endpoint the phantom had been using before
 3. The sstable2json output seems to include multiple sub-sections for each 
 handoff with the same deletedAt information.
 The phantom handoff endpoint changes after a non-zero handoff comes through:
  INFO [HintedHandoff:1] 2012-12-11 06:57:35,093 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.1
  INFO [HintedHandoff:1] 2012-12-11 07:07:35,092 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.1
  INFO [HintedHandoff:1] 2012-12-11 07:07:37,915 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 1058 rows to endpoint /10.10.10.2
  INFO [HintedHandoff:1] 2012-12-11 07:17:35,093 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.2
  INFO [HintedHandoff:1] 2012-12-11 07:27:35,093 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.2
 Sometimes a non-zero handoff will be immediately followed by an off 
 schedule phantom handoff to the endpoint the phantom had been using before:
  INFO [HintedHandoff:1] 2012-12-12 21:47:39,335 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.3
  INFO [HintedHandoff:1] 2012-12-12 21:57:39,335 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.3
  INFO [HintedHandoff:1] 2012-12-12 22:07:43,319 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 1416 rows to endpoint /10.10.10.4
  INFO [HintedHandoff:1] 2012-12-12 22:07:43,320 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.3
  INFO [HintedHandoff:1] 2012-12-12 22:17:39,357 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.4
  INFO [HintedHandoff:1] 2012-12-12 22:27:39,337 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.4
 The first few entries from one of the json files:
 {
 0aaa: {
 ccf5dc203a2211e2e154da71a9bb: {
 deletedAt: -9223372036854775808, 
 subColumns: []
 }, 
 ccf603303a2211e2e154da71a9bb: {
 deletedAt: -9223372036854775808, 
 subColumns: []
 }, 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-5068) CLONE - Once a host has been hinted to, log messages for it repeat every 10 mins even if no hints are delivered

2013-02-05 Thread Peter Haggerty (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Haggerty updated CASSANDRA-5068:
--

Affects Version/s: 1.1.8
   1.1.9

 CLONE - Once a host has been hinted to, log messages for it repeat every 10 
 mins even if no hints are delivered
 ---

 Key: CASSANDRA-5068
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5068
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.6, 1.1.8, 1.1.9, 1.2.0
 Environment: cassandra 1.1.6
 java 1.6.0_30
Reporter: Peter Haggerty
Assignee: Brandon Williams
Priority: Minor
  Labels: hinted, hintedhandoff
 Attachments: 5068.txt


 We have 0 row hinted handoffs every 10 minutes like clockwork. This impacts 
 our ability to monitor the cluster by adding persistent noise in the handoff 
 metric.
 Previous mentions of this issue are here:
 http://www.mail-archive.com/user@cassandra.apache.org/msg25982.html
 The hinted handoffs can be scrubbed away with
 nodetool -h 127.0.0.1 scrub system HintsColumnFamily
 but they return after anywhere from a few minutes to multiple hours later.
 These started to appear after an upgrade to 1.1.6 and haven't gone away 
 despite rolling cleanups, rolling restarts, multiple rounds of scrubbing, etc.
 A few things we've noticed about the handoffs:
 1. The phantom handoff endpoint changes after a non-zero handoff comes through
 2. Sometimes a non-zero handoff will be immediately followed by an off 
 schedule phantom handoff to the endpoint the phantom had been using before
 3. The sstable2json output seems to include multiple sub-sections for each 
 handoff with the same deletedAt information.
 The phantom handoff endpoint changes after a non-zero handoff comes through:
  INFO [HintedHandoff:1] 2012-12-11 06:57:35,093 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.1
  INFO [HintedHandoff:1] 2012-12-11 07:07:35,092 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.1
  INFO [HintedHandoff:1] 2012-12-11 07:07:37,915 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 1058 rows to endpoint /10.10.10.2
  INFO [HintedHandoff:1] 2012-12-11 07:17:35,093 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.2
  INFO [HintedHandoff:1] 2012-12-11 07:27:35,093 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.2
 Sometimes a non-zero handoff will be immediately followed by an off 
 schedule phantom handoff to the endpoint the phantom had been using before:
  INFO [HintedHandoff:1] 2012-12-12 21:47:39,335 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.3
  INFO [HintedHandoff:1] 2012-12-12 21:57:39,335 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.3
  INFO [HintedHandoff:1] 2012-12-12 22:07:43,319 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 1416 rows to endpoint /10.10.10.4
  INFO [HintedHandoff:1] 2012-12-12 22:07:43,320 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.3
  INFO [HintedHandoff:1] 2012-12-12 22:17:39,357 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.4
  INFO [HintedHandoff:1] 2012-12-12 22:27:39,337 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.4
 The first few entries from one of the json files:
 {
 0aaa: {
 ccf5dc203a2211e2e154da71a9bb: {
 deletedAt: -9223372036854775808, 
 subColumns: []
 }, 
 ccf603303a2211e2e154da71a9bb: {
 deletedAt: -9223372036854775808, 
 subColumns: []
 }, 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-5068) CLONE - Once a host has been hinted to, log messages for it repeat every 10 mins even if no hints are delivered


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brandon Williams updated CASSANDRA-5068:


Affects Version/s: (was: 1.1.9)
   (was: 1.1.8)
   (was: 1.2.0)

 CLONE - Once a host has been hinted to, log messages for it repeat every 10 
 mins even if no hints are delivered
 ---

 Key: CASSANDRA-5068
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5068
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.6
 Environment: cassandra 1.1.6
 java 1.6.0_30
Reporter: Peter Haggerty
Assignee: Brandon Williams
Priority: Minor
  Labels: hinted, hintedhandoff
 Attachments: 5068.txt


 We have 0 row hinted handoffs every 10 minutes like clockwork. This impacts 
 our ability to monitor the cluster by adding persistent noise in the handoff 
 metric.
 Previous mentions of this issue are here:
 http://www.mail-archive.com/user@cassandra.apache.org/msg25982.html
 The hinted handoffs can be scrubbed away with
 nodetool -h 127.0.0.1 scrub system HintsColumnFamily
 but they return after anywhere from a few minutes to multiple hours later.
 These started to appear after an upgrade to 1.1.6 and haven't gone away 
 despite rolling cleanups, rolling restarts, multiple rounds of scrubbing, etc.
 A few things we've noticed about the handoffs:
 1. The phantom handoff endpoint changes after a non-zero handoff comes through
 2. Sometimes a non-zero handoff will be immediately followed by an off 
 schedule phantom handoff to the endpoint the phantom had been using before
 3. The sstable2json output seems to include multiple sub-sections for each 
 handoff with the same deletedAt information.
 The phantom handoff endpoint changes after a non-zero handoff comes through:
  INFO [HintedHandoff:1] 2012-12-11 06:57:35,093 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.1
  INFO [HintedHandoff:1] 2012-12-11 07:07:35,092 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.1
  INFO [HintedHandoff:1] 2012-12-11 07:07:37,915 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 1058 rows to endpoint /10.10.10.2
  INFO [HintedHandoff:1] 2012-12-11 07:17:35,093 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.2
  INFO [HintedHandoff:1] 2012-12-11 07:27:35,093 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.2
 Sometimes a non-zero handoff will be immediately followed by an off 
 schedule phantom handoff to the endpoint the phantom had been using before:
  INFO [HintedHandoff:1] 2012-12-12 21:47:39,335 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.3
  INFO [HintedHandoff:1] 2012-12-12 21:57:39,335 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.3
  INFO [HintedHandoff:1] 2012-12-12 22:07:43,319 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 1416 rows to endpoint /10.10.10.4
  INFO [HintedHandoff:1] 2012-12-12 22:07:43,320 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.3
  INFO [HintedHandoff:1] 2012-12-12 22:17:39,357 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.4
  INFO [HintedHandoff:1] 2012-12-12 22:27:39,337 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.4
 The first few entries from one of the json files:
 {
 0aaa: {
 ccf5dc203a2211e2e154da71a9bb: {
 deletedAt: -9223372036854775808, 
 subColumns: []
 }, 
 ccf603303a2211e2e154da71a9bb: {
 deletedAt: -9223372036854775808, 
 subColumns: []
 }, 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Cassandra Wiki] Trivial Update of Georgetta by Georgetta

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The Georgetta page has been changed by Georgetta:
http://wiki.apache.org/cassandra/Georgetta?action=diffrev1=2rev2=3

- Hey !! The name is NICOLE GILLIAM. I am staying at Oxford.BR
- I go to night school at The Weird School which has a branch in Scottsdale. I 
am planning to become a Author. I like YoYo. My papa name is Karl  and he is a 
Physiotherapist. My momy is a Childcare worker.BR
+ Yo bros !! I am LIZZETTE POWELL. I have a house in Seaside.BR
+ My parents want me to join The Horrid School built at Clarke County. I am 
working as Examiner. I like Sewing. My father name is Randall  and he is a 
Politician. My mother is a Coachman.BR
  BR
- My page [[http://discountlouisvuittonrespectonline.webs.com|cheap louis 
vuitton bags]]
+ my weblog; [[http://discountlouisvuittonrespectonline.webs.com|louis vuitton 
iphone 4 case]]

[jira] [Commented] (CASSANDRA-5068) CLONE - Once a host has been hinted to, log messages for it repeat every 10 mins even if no hints are delivered


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571782#comment-13571782
 ] 

Brandon Williams commented on CASSANDRA-5068:
-

bq. Shouldn't the I have  X % tombstones in this sstable code kick in?

As in the tombstone-aggressive code in STS?  I suspect we're ending up under 
the min compaction threshold all the time.

 CLONE - Once a host has been hinted to, log messages for it repeat every 10 
 mins even if no hints are delivered
 ---

 Key: CASSANDRA-5068
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5068
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.6
 Environment: cassandra 1.1.6
 java 1.6.0_30
Reporter: Peter Haggerty
Assignee: Brandon Williams
Priority: Minor
  Labels: hinted, hintedhandoff
 Attachments: 5068.txt


 We have 0 row hinted handoffs every 10 minutes like clockwork. This impacts 
 our ability to monitor the cluster by adding persistent noise in the handoff 
 metric.
 Previous mentions of this issue are here:
 http://www.mail-archive.com/user@cassandra.apache.org/msg25982.html
 The hinted handoffs can be scrubbed away with
 nodetool -h 127.0.0.1 scrub system HintsColumnFamily
 but they return after anywhere from a few minutes to multiple hours later.
 These started to appear after an upgrade to 1.1.6 and haven't gone away 
 despite rolling cleanups, rolling restarts, multiple rounds of scrubbing, etc.
 A few things we've noticed about the handoffs:
 1. The phantom handoff endpoint changes after a non-zero handoff comes through
 2. Sometimes a non-zero handoff will be immediately followed by an off 
 schedule phantom handoff to the endpoint the phantom had been using before
 3. The sstable2json output seems to include multiple sub-sections for each 
 handoff with the same deletedAt information.
 The phantom handoff endpoint changes after a non-zero handoff comes through:
  INFO [HintedHandoff:1] 2012-12-11 06:57:35,093 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.1
  INFO [HintedHandoff:1] 2012-12-11 07:07:35,092 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.1
  INFO [HintedHandoff:1] 2012-12-11 07:07:37,915 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 1058 rows to endpoint /10.10.10.2
  INFO [HintedHandoff:1] 2012-12-11 07:17:35,093 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.2
  INFO [HintedHandoff:1] 2012-12-11 07:27:35,093 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.2
 Sometimes a non-zero handoff will be immediately followed by an off 
 schedule phantom handoff to the endpoint the phantom had been using before:
  INFO [HintedHandoff:1] 2012-12-12 21:47:39,335 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.3
  INFO [HintedHandoff:1] 2012-12-12 21:57:39,335 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.3
  INFO [HintedHandoff:1] 2012-12-12 22:07:43,319 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 1416 rows to endpoint /10.10.10.4
  INFO [HintedHandoff:1] 2012-12-12 22:07:43,320 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.3
  INFO [HintedHandoff:1] 2012-12-12 22:17:39,357 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.4
  INFO [HintedHandoff:1] 2012-12-12 22:27:39,337 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.4
 The first few entries from one of the json files:
 {
 0aaa: {
 ccf5dc203a2211e2e154da71a9bb: {
 deletedAt: -9223372036854775808, 
 subColumns: []
 }, 
 ccf603303a2211e2e154da71a9bb: {
 deletedAt: -9223372036854775808, 
 subColumns: []
 }, 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-5186) Schema NPEs in 1.1.6. Upgrading to 1.1.9 causes IllegalArgumentException loading Schema

2013-02-05 Thread Carl Yeksigian (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carl Yeksigian updated CASSANDRA-5186:
--

Attachment: 5186.patch

 Schema NPEs in 1.1.6.  Upgrading to 1.1.9 causes IllegalArgumentException 
 loading Schema
 

 Key: CASSANDRA-5186
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5186
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.9
Reporter: Michael Harris
Priority: Critical
 Attachments: 5186.patch


 We experienced the problems described in CASSANDRA-4219 in version 1.1.6.  We 
 were told to upgrade to 1.1.9.  Now the schema fails to load with the 
 following error:
 java.lang.IllegalArgumentException: value already present: 1105
 at com.google.common.base.Preconditions.checkArgument(Preconditions.java:115)
 at 
 com.google.common.collect.AbstractBiMap.putInBothMaps(AbstractBiMap.java:112)
 at com.google.common.collect.AbstractBiMap.put(AbstractBiMap.java:96)
 at com.google.common.collect.HashBiMap.put(HashBiMap.java:85)
 at org.apache.cassandra.config.Schema.load(Schema.java:399)
 at org.apache.cassandra.config.Schema.load(Schema.java:120)
 at org.apache.cassandra.config.Schema.load(Schema.java:105)
 at 
 org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescriptor.java:534)
 at 
 org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandraDaemon.java:183)
 at 
 com.palantir.phoenix.datastore.cass.server.PTCassandraServer$PTCassandraDaemon.setup(PTCassandraServer.java:64)
 at 
 org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:389)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-5186) Schema NPEs in 1.1.6. Upgrading to 1.1.9 causes IllegalArgumentException loading Schema

2013-02-05 Thread Carl Yeksigian (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571800#comment-13571800
 ] 

Carl Yeksigian commented on CASSANDRA-5186:
---

Sorry, I misread this code before. Since it is a bimap, it's possible that 
there are two cfs with the same ID but different names. I've attached a patch 
that will throw an exception with that information; hopefully that will help 
with debugging the issue.

 Schema NPEs in 1.1.6.  Upgrading to 1.1.9 causes IllegalArgumentException 
 loading Schema
 

 Key: CASSANDRA-5186
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5186
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.9
Reporter: Michael Harris
Priority: Critical
 Attachments: 5186.patch


 We experienced the problems described in CASSANDRA-4219 in version 1.1.6.  We 
 were told to upgrade to 1.1.9.  Now the schema fails to load with the 
 following error:
 java.lang.IllegalArgumentException: value already present: 1105
 at com.google.common.base.Preconditions.checkArgument(Preconditions.java:115)
 at 
 com.google.common.collect.AbstractBiMap.putInBothMaps(AbstractBiMap.java:112)
 at com.google.common.collect.AbstractBiMap.put(AbstractBiMap.java:96)
 at com.google.common.collect.HashBiMap.put(HashBiMap.java:85)
 at org.apache.cassandra.config.Schema.load(Schema.java:399)
 at org.apache.cassandra.config.Schema.load(Schema.java:120)
 at org.apache.cassandra.config.Schema.load(Schema.java:105)
 at 
 org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescriptor.java:534)
 at 
 org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandraDaemon.java:183)
 at 
 com.palantir.phoenix.datastore.cass.server.PTCassandraServer$PTCassandraDaemon.setup(PTCassandraServer.java:64)
 at 
 org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:389)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-5186) Schema NPEs in 1.1.6. Upgrading to 1.1.9 causes IllegalArgumentException loading Schema

2013-02-05 Thread Michael Harris (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571808#comment-13571808
 ] 

Michael Harris commented on CASSANDRA-5186:
---

so, do you want us to apply this patch and get back to you with the exception?  
I'm not exactly sure how that's going to help you debug this, but we can do it 
if you want.

 Schema NPEs in 1.1.6.  Upgrading to 1.1.9 causes IllegalArgumentException 
 loading Schema
 

 Key: CASSANDRA-5186
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5186
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.9
Reporter: Michael Harris
Priority: Critical
 Attachments: 5186.patch


 We experienced the problems described in CASSANDRA-4219 in version 1.1.6.  We 
 were told to upgrade to 1.1.9.  Now the schema fails to load with the 
 following error:
 java.lang.IllegalArgumentException: value already present: 1105
 at com.google.common.base.Preconditions.checkArgument(Preconditions.java:115)
 at 
 com.google.common.collect.AbstractBiMap.putInBothMaps(AbstractBiMap.java:112)
 at com.google.common.collect.AbstractBiMap.put(AbstractBiMap.java:96)
 at com.google.common.collect.HashBiMap.put(HashBiMap.java:85)
 at org.apache.cassandra.config.Schema.load(Schema.java:399)
 at org.apache.cassandra.config.Schema.load(Schema.java:120)
 at org.apache.cassandra.config.Schema.load(Schema.java:105)
 at 
 org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescriptor.java:534)
 at 
 org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandraDaemon.java:183)
 at 
 com.palantir.phoenix.datastore.cass.server.PTCassandraServer$PTCassandraDaemon.setup(PTCassandraServer.java:64)
 at 
 org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:389)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-5068) CLONE - Once a host has been hinted to, log messages for it repeat every 10 mins even if no hints are delivered


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brandon Williams updated CASSANDRA-5068:


 Reviewer: jbellis
   Tester: enigmacurry
Fix Version/s: 1.2.2
   1.1.10

 CLONE - Once a host has been hinted to, log messages for it repeat every 10 
 mins even if no hints are delivered
 ---

 Key: CASSANDRA-5068
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5068
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.6
 Environment: cassandra 1.1.6
 java 1.6.0_30
Reporter: Peter Haggerty
Assignee: Brandon Williams
Priority: Minor
  Labels: hinted, hintedhandoff
 Fix For: 1.1.10, 1.2.2

 Attachments: 5068.txt


 We have 0 row hinted handoffs every 10 minutes like clockwork. This impacts 
 our ability to monitor the cluster by adding persistent noise in the handoff 
 metric.
 Previous mentions of this issue are here:
 http://www.mail-archive.com/user@cassandra.apache.org/msg25982.html
 The hinted handoffs can be scrubbed away with
 nodetool -h 127.0.0.1 scrub system HintsColumnFamily
 but they return after anywhere from a few minutes to multiple hours later.
 These started to appear after an upgrade to 1.1.6 and haven't gone away 
 despite rolling cleanups, rolling restarts, multiple rounds of scrubbing, etc.
 A few things we've noticed about the handoffs:
 1. The phantom handoff endpoint changes after a non-zero handoff comes through
 2. Sometimes a non-zero handoff will be immediately followed by an off 
 schedule phantom handoff to the endpoint the phantom had been using before
 3. The sstable2json output seems to include multiple sub-sections for each 
 handoff with the same deletedAt information.
 The phantom handoff endpoint changes after a non-zero handoff comes through:
  INFO [HintedHandoff:1] 2012-12-11 06:57:35,093 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.1
  INFO [HintedHandoff:1] 2012-12-11 07:07:35,092 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.1
  INFO [HintedHandoff:1] 2012-12-11 07:07:37,915 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 1058 rows to endpoint /10.10.10.2
  INFO [HintedHandoff:1] 2012-12-11 07:17:35,093 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.2
  INFO [HintedHandoff:1] 2012-12-11 07:27:35,093 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.2
 Sometimes a non-zero handoff will be immediately followed by an off 
 schedule phantom handoff to the endpoint the phantom had been using before:
  INFO [HintedHandoff:1] 2012-12-12 21:47:39,335 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.3
  INFO [HintedHandoff:1] 2012-12-12 21:57:39,335 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.3
  INFO [HintedHandoff:1] 2012-12-12 22:07:43,319 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 1416 rows to endpoint /10.10.10.4
  INFO [HintedHandoff:1] 2012-12-12 22:07:43,320 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.3
  INFO [HintedHandoff:1] 2012-12-12 22:17:39,357 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.4
  INFO [HintedHandoff:1] 2012-12-12 22:27:39,337 HintedHandOffManager.java 
 (line 392) Finished hinted handoff of 0 rows to endpoint /10.10.10.4
 The first few entries from one of the json files:
 {
 0aaa: {
 ccf5dc203a2211e2e154da71a9bb: {
 deletedAt: -9223372036854775808, 
 subColumns: []
 }, 
 ccf603303a2211e2e154da71a9bb: {
 deletedAt: -9223372036854775808, 
 subColumns: []
 }, 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Cassandra Wiki] Trivial Update of ClarkABN by ClarkABN

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The ClarkABN page has been changed by ClarkABN:
http://wiki.apache.org/cassandra/ClarkABN?action=diffrev1=2rev2=3

- Yo bros !! My name is JACQULYN BROWNING. I live in Saginaw.BR
- Soon i will turn 56. I want to become a Receptionist. One day i would want to 
do Video Games. My dad name is Douglas  and he is a Broker. My mummy is a 
Blacksmith.BR
+ Hi !! I am SIGRID SOTO. I am staying at Columbus.BR
+ I am turning 37. I work as a Spy. My hobby is Airbrushing. My daddy name is 
Kelly  and he is a Minister. My momy is a Police Detective.BR
  BR
- Feel free to surf to my site ... 
[[http://michael-kors-shoes.blinkweb.com|michael kors watch]]
+ Here is my blog ... [[http://michael-kors-handbag.blinkweb.com|michael kors 
rose gold watch]]

[Cassandra Wiki] Trivial Update of HarrisonC by HarrisonC

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The HarrisonC page has been changed by HarrisonC:
http://wiki.apache.org/cassandra/HarrisonC

New page:
I belong to Lacey. I am 29. I and my sister go to The Colossal School of Tough 
People located in San Jose.BR
I work as a Presenter. I also like to Needlepoint.BR
BR
Here is my page [[http://drdrebeatscheap.blinkweb.com|dre beats cheap]]

[jira] [Commented] (CASSANDRA-5224) alter table add in CQL3 allows adding columns to COMPACT STORAGE tables


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571846#comment-13571846
 ] 

Aleksey Yeschenko commented on CASSANDRA-5224:
--

bq. it appears that the metadata, however, is not defined correctly.
Can you elaborate?

As for adding a column - not all tables defined with COMPACT STORAGE are in 
fact 'compact' as far as CFDefinition is concerned. It's allowed to add columns 
to pre-cql3 'static' cfs, even though you have to defined them with COMPACT 
STORAGE in cql3 (won't use a composite comparator under the hood).

 alter table add in CQL3 allows adding columns to COMPACT STORAGE tables
 ---

 Key: CASSANDRA-5224
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5224
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.2.1
Reporter: Michael Kjellman
Assignee: Aleksey Yeschenko
Priority: Minor
 Fix For: 1.2.2


 From the docs:
 These additions to a table are not allowed:
 Adding a column having the same name as an existing column.
 Adding columns to tables defined with COMPACT STORAGE.
 however, this still works against a domain defined with COMPACT STORAGE in 
 cqlsh
 it appears that the metadata, however, is not defined correctly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Comment Edited] (CASSANDRA-5224) alter table add in CQL3 allows adding columns to COMPACT STORAGE tables

[
https://issues.apache.org/jira/browse/CASSANDRA-5224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571846#comment-13571846
]

Aleksey Yeschenko edited comment on CASSANDRA-5224 at 2/5/13 11:01 PM:
---

bq. it appears that the metadata, however, is not defined correctly.
Can you elaborate?

As for adding a column - not all tables defined with COMPACT STORAGE are in
fact 'compact' as far as CFDefinition is concerned. It's allowed to add columns
to pre-cql3 'static' cfs, even though you have to define them with COMPACT
STORAGE in cql3 (won't use a composite comparator under the hood).

was (Author: iamaleksey):
bq. it appears that the metadata, however, is not defined correctly.
Can you elaborate?

As for adding a column - not all tables defined with COMPACT STORAGE are in
fact 'compact' as far as CFDefinition is concerned. It's allowed to add columns
to pre-cql3 'static' cfs, even though you have to defined them with COMPACT
STORAGE in cql3 (won't use a composite comparator under the hood).

alter table add in CQL3 allows adding columns to COMPACT STORAGE tables
---

Key: CASSANDRA-5224
URL: https://issues.apache.org/jira/browse/CASSANDRA-5224
Project: Cassandra
Issue Type: Bug
Affects Versions: 1.2.1
Reporter: Michael Kjellman
Assignee: Aleksey Yeschenko
Priority: Minor
Fix For: 1.2.2

From the docs:
These additions to a table are not allowed:
Adding a column having the same name as an existing column.
Adding columns to tables defined with COMPACT STORAGE.
however, this still works against a domain defined with COMPACT STORAGE in
cqlsh
it appears that the metadata, however, is not defined correctly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-4464) expose 2I CFs to the rest of nodetool

[
https://issues.apache.org/jira/browse/CASSANDRA-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571849#comment-13571849
]

Brandon Williams commented on CASSANDRA-4464:
-

bq. cfstats - now prints out 2I info, ordered below owning CF

Actually, it's after all regular CFs but I don't care much either way.

bq. snapshot - now throws an exception when attempting to snapshot a 2I

A better exception than saying that the CF does not exist might be better here,
but overall this looks good.

expose 2I CFs to the rest of nodetool
-

Key: CASSANDRA-4464
URL: https://issues.apache.org/jira/browse/CASSANDRA-4464
Project: Cassandra
Issue Type: New Feature
Components: Tools
Reporter: Jonathan Ellis
Assignee: Jason Brown
Priority: Minor
Fix For: 1.2.2

Attachments: 4464.txt, 4464-v1.patch, 4464-v2.patch

This was begun in CASSANDRA-4063. We should extend it to scrub as well, and
probably compact since any sane way to do it for scrub should give the other
for free.
Not sure how easy these will be since they go through CompactionManager via
StorageProxy. I think getValidColumnFamilies could be updated to check for
index CFs with dot notation.
(Other operations like flush or snapshot don't make sense for 2I CFs in
isolation of their parent.)

[jira] [Commented] (CASSANDRA-5224) alter table add in CQL3 allows adding columns to COMPACT STORAGE tables

2013-02-05 Thread Michael Kjellman (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571851#comment-13571851
 ] 

Michael Kjellman commented on CASSANDRA-5224:
-

the metadata is not defined correctly but was a bug on my end (so you can 
ignore it). I hadn't gotten around to updating the bug yet. apologies.

so i'm confused though, a describe table shows that the legacy table is defined 
in cql3 as COMPACT STORAGE, so an alter table blah add blah is doing a static 
cql2 table while in cql3 mode?

 alter table add in CQL3 allows adding columns to COMPACT STORAGE tables
 ---

 Key: CASSANDRA-5224
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5224
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.2.1
Reporter: Michael Kjellman
Assignee: Aleksey Yeschenko
Priority: Minor
 Fix For: 1.2.2


 From the docs:
 These additions to a table are not allowed:
 Adding a column having the same name as an existing column.
 Adding columns to tables defined with COMPACT STORAGE.
 however, this still works against a domain defined with COMPACT STORAGE in 
 cqlsh
 it appears that the metadata, however, is not defined correctly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-5224) alter table add in CQL3 allows adding columns to COMPACT STORAGE tables


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571876#comment-13571876
 ] 

Aleksey Yeschenko commented on CASSANDRA-5224:
--

Oh I won't argue that it's somewhat confusing. DESCRIBE TABLE will *NOT* output 
WITH COMPACT STORAGE only for sparse composite cfs. Read CFDefinition 
constructor code if you are interested in the details (and/or 
pylib/cqlshlib/cql3handling.py lines 1466:1478 for my take on it).

 alter table add in CQL3 allows adding columns to COMPACT STORAGE tables
 ---

 Key: CASSANDRA-5224
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5224
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.2.1
Reporter: Michael Kjellman
Assignee: Aleksey Yeschenko
Priority: Minor
 Fix For: 1.2.2


 From the docs:
 These additions to a table are not allowed:
 Adding a column having the same name as an existing column.
 Adding columns to tables defined with COMPACT STORAGE.
 however, this still works against a domain defined with COMPACT STORAGE in 
 cqlsh
 it appears that the metadata, however, is not defined correctly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-5186) Schema NPEs in 1.1.6. Upgrading to 1.1.9 causes IllegalArgumentException loading Schema


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571878#comment-13571878
 ] 

Jonathan Ellis commented on CASSANDRA-5186:
---

If you've done concurrent schema changes such that two CFs got the same ID on 
different machines you're SOL on any version.  You'll need to blow away the 
schema and recreate it. (1.2 should avoid getting into this situation in the 
first place, but upgrading won't fix it once you're already there.)

 Schema NPEs in 1.1.6.  Upgrading to 1.1.9 causes IllegalArgumentException 
 loading Schema
 

 Key: CASSANDRA-5186
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5186
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.9
Reporter: Michael Harris
Priority: Critical
 Attachments: 5186.patch


 We experienced the problems described in CASSANDRA-4219 in version 1.1.6.  We 
 were told to upgrade to 1.1.9.  Now the schema fails to load with the 
 following error:
 java.lang.IllegalArgumentException: value already present: 1105
 at com.google.common.base.Preconditions.checkArgument(Preconditions.java:115)
 at 
 com.google.common.collect.AbstractBiMap.putInBothMaps(AbstractBiMap.java:112)
 at com.google.common.collect.AbstractBiMap.put(AbstractBiMap.java:96)
 at com.google.common.collect.HashBiMap.put(HashBiMap.java:85)
 at org.apache.cassandra.config.Schema.load(Schema.java:399)
 at org.apache.cassandra.config.Schema.load(Schema.java:120)
 at org.apache.cassandra.config.Schema.load(Schema.java:105)
 at 
 org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescriptor.java:534)
 at 
 org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandraDaemon.java:183)
 at 
 com.palantir.phoenix.datastore.cass.server.PTCassandraServer$PTCassandraDaemon.setup(PTCassandraServer.java:64)
 at 
 org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:389)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-5196) IllegalStateException thrown when running new installation with old data directories


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571881#comment-13571881
 ] 

Brandon Williams commented on CASSANDRA-5196:
-

+1 on the patch, but I don't understand what the directory creation problem is 
in the case of it existing as user X, but then even running as root we raise an 
error.

 IllegalStateException thrown when running new installation with old data 
 directories
 

 Key: CASSANDRA-5196
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5196
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.2.1
 Environment: CentOS 5.5
Reporter: Robbie Strickland
Assignee: Aleksey Yeschenko
Priority: Minor
 Fix For: 1.2.2

 Attachments: 5196.txt


 If you install 1.2.1 when there are existing data directories, the scrub 
 operation fails, throwing this exception:
 ERROR [main] 2013-01-29 15:05:06,564 FileUtils.java (line 373) Stopping the 
 gossiper and the RPC server
 ERROR [main] 2013-01-29 15:05:06,564 CassandraDaemon.java (line 387) 
 Exception encountered during startup
 java.lang.IllegalStateException: No configured daemon
   at 
 org.apache.cassandra.service.StorageService.stopRPCServer(StorageService.java:314)
   at 
 org.apache.cassandra.io.util.FileUtils.handleFSError(FileUtils.java:375)
   at org.apache.cassandra.db.Directories.init(Directories.java:113)
   at org.apache.cassandra.db.Directories.create(Directories.java:91)
   at 
 org.apache.cassandra.db.ColumnFamilyStore.scrubDataDirectories(ColumnFamilyStore.java:403)
   at 
 org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:174)
   at 
 org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:370)
   at 
 org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:413)
 This condition should produce a more reasonable exception.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CASSANDRA-5224) alter table add in CQL3 allows adding columns to COMPACT STORAGE tables


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Yeschenko resolved CASSANDRA-5224.
--

Resolution: Not A Problem

 alter table add in CQL3 allows adding columns to COMPACT STORAGE tables
 ---

 Key: CASSANDRA-5224
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5224
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.2.1
Reporter: Michael Kjellman
Assignee: Aleksey Yeschenko
Priority: Minor
 Fix For: 1.2.2


 From the docs:
 These additions to a table are not allowed:
 Adding a column having the same name as an existing column.
 Adding columns to tables defined with COMPACT STORAGE.
 however, this still works against a domain defined with COMPACT STORAGE in 
 cqlsh
 it appears that the metadata, however, is not defined correctly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-5196) IllegalStateException thrown when running new installation with old data directories


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571888#comment-13571888
 ] 

Aleksey Yeschenko commented on CASSANDRA-5196:
--

bq. but I don't understand what the directory creation problem is in the case 
of it existing as user X, but then even running as root we raise an error.

I don't understand either - and I can't reproduce it (I tried).

 IllegalStateException thrown when running new installation with old data 
 directories
 

 Key: CASSANDRA-5196
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5196
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.2.1
 Environment: CentOS 5.5
Reporter: Robbie Strickland
Assignee: Aleksey Yeschenko
Priority: Minor
 Fix For: 1.2.2

 Attachments: 5196.txt


 If you install 1.2.1 when there are existing data directories, the scrub 
 operation fails, throwing this exception:
 ERROR [main] 2013-01-29 15:05:06,564 FileUtils.java (line 373) Stopping the 
 gossiper and the RPC server
 ERROR [main] 2013-01-29 15:05:06,564 CassandraDaemon.java (line 387) 
 Exception encountered during startup
 java.lang.IllegalStateException: No configured daemon
   at 
 org.apache.cassandra.service.StorageService.stopRPCServer(StorageService.java:314)
   at 
 org.apache.cassandra.io.util.FileUtils.handleFSError(FileUtils.java:375)
   at org.apache.cassandra.db.Directories.init(Directories.java:113)
   at org.apache.cassandra.db.Directories.create(Directories.java:91)
   at 
 org.apache.cassandra.db.ColumnFamilyStore.scrubDataDirectories(ColumnFamilyStore.java:403)
   at 
 org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:174)
   at 
 org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:370)
   at 
 org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:413)
 This condition should produce a more reasonable exception.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-4464) expose 2I CFs to the rest of nodetool

2013-02-05 Thread Jason Brown (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571893#comment-13571893
 ] 

Jason Brown commented on CASSANDRA-4464:


Anything you think I should clean up here, or it is shippable?

 expose 2I CFs to the rest of nodetool
 -

 Key: CASSANDRA-4464
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4464
 Project: Cassandra
  Issue Type: New Feature
  Components: Tools
Reporter: Jonathan Ellis
Assignee: Jason Brown
Priority: Minor
 Fix For: 1.2.2

 Attachments: 4464.txt, 4464-v1.patch, 4464-v2.patch


 This was begun in CASSANDRA-4063.  We should extend it to scrub as well, and 
 probably compact since any sane way to do it for scrub should give the other 
 for free.
 Not sure how easy these will be since they go through CompactionManager via 
 StorageProxy.  I think getValidColumnFamilies could be updated to check for 
 index CFs with dot notation.
 (Other operations like flush or snapshot don't make sense for 2I CFs in 
 isolation of their parent.)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-4464) expose 2I CFs to the rest of nodetool


[ 
https://issues.apache.org/jira/browse/CASSANDRA-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571904#comment-13571904
 ] 

Brandon Williams commented on CASSANDRA-4464:
-

It would be nice to catch the 2I snapshot attempt and throw a relevant error so 
it doesn't confuse anyone (any further, since they're already trying to do 
something bad ;)

 expose 2I CFs to the rest of nodetool
 -

 Key: CASSANDRA-4464
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4464
 Project: Cassandra
  Issue Type: New Feature
  Components: Tools
Reporter: Jonathan Ellis
Assignee: Jason Brown
Priority: Minor
 Fix For: 1.2.2

 Attachments: 4464.txt, 4464-v1.patch, 4464-v2.patch


 This was begun in CASSANDRA-4063.  We should extend it to scrub as well, and 
 probably compact since any sane way to do it for scrub should give the other 
 for free.
 Not sure how easy these will be since they go through CompactionManager via 
 StorageProxy.  I think getValidColumnFamilies could be updated to check for 
 index CFs with dot notation.
 (Other operations like flush or snapshot don't make sense for 2I CFs in 
 isolation of their parent.)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-5196) IllegalStateException thrown when running new installation with old data directories


[ 
https://issues.apache.org/jira/browse/CASSANDRA-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571915#comment-13571915
 ] 

Brandon Williams commented on CASSANDRA-5196:
-

We can take a closer with the patch in place if it happens again.

 IllegalStateException thrown when running new installation with old data 
 directories
 

 Key: CASSANDRA-5196
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5196
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.2.1
 Environment: CentOS 5.5
Reporter: Robbie Strickland
Assignee: Aleksey Yeschenko
Priority: Minor
 Fix For: 1.2.2

 Attachments: 5196.txt


 If you install 1.2.1 when there are existing data directories, the scrub 
 operation fails, throwing this exception:
 ERROR [main] 2013-01-29 15:05:06,564 FileUtils.java (line 373) Stopping the 
 gossiper and the RPC server
 ERROR [main] 2013-01-29 15:05:06,564 CassandraDaemon.java (line 387) 
 Exception encountered during startup
 java.lang.IllegalStateException: No configured daemon
   at 
 org.apache.cassandra.service.StorageService.stopRPCServer(StorageService.java:314)
   at 
 org.apache.cassandra.io.util.FileUtils.handleFSError(FileUtils.java:375)
   at org.apache.cassandra.db.Directories.init(Directories.java:113)
   at org.apache.cassandra.db.Directories.create(Directories.java:91)
   at 
 org.apache.cassandra.db.ColumnFamilyStore.scrubDataDirectories(ColumnFamilyStore.java:403)
   at 
 org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:174)
   at 
 org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:370)
   at 
 org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:413)
 This condition should produce a more reasonable exception.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-4464) expose 2I CFs to the rest of nodetool

2013-02-05 Thread Jason Brown (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571918#comment-13571918
 ] 

Jason Brown commented on CASSANDRA-4464:


np, will do.

 expose 2I CFs to the rest of nodetool
 -

 Key: CASSANDRA-4464
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4464
 Project: Cassandra
  Issue Type: New Feature
  Components: Tools
Reporter: Jonathan Ellis
Assignee: Jason Brown
Priority: Minor
 Fix For: 1.2.2

 Attachments: 4464.txt, 4464-v1.patch, 4464-v2.patch


 This was begun in CASSANDRA-4063.  We should extend it to scrub as well, and 
 probably compact since any sane way to do it for scrub should give the other 
 for free.
 Not sure how easy these will be since they go through CompactionManager via 
 StorageProxy.  I think getValidColumnFamilies could be updated to check for 
 index CFs with dot notation.
 (Other operations like flush or snapshot don't make sense for 2I CFs in 
 isolation of their parent.)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Cassandra Wiki] Trivial Update of Steve64N by Steve64N