date:20130401

Dear Wiki user,

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

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

New page:
My name: Merissa HurdBR
Age: 23BR
Country: ItaliaBR
Town: Ternate BR
Post code: 21020BR
Address: Via Spalato 13BR
BR
Review my page: [[http://paydayloansonlinehut.om/|Payday Loans Online]]

[jira] [Commented] (CASSANDRA-5381) java.io.EOFException exception while executing nodetool repair with compression enabled

2013-04-01 Thread Neil Thomson (JIRA)


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

Neil Thomson commented on CASSANDRA-5381:
-

Hi, yes we also have node encryption enabled.

 java.io.EOFException exception while executing nodetool repair with 
 compression enabled
 ---

 Key: CASSANDRA-5381
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5381
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.2.3
 Environment: Linux Virtual Machines, Red Hat Enterprise release 6.4, 
 kernel version  2.6.32-358.2.1.el6.x86_64. Each VM has 8GB memory and 4vCPUS.
Reporter: Neil Thomson
Priority: Minor

 Very similar to issue reported in CASSANDRA-5105. I have 3 nodes configured 
 in a cluster. The nodes are configured with compression enabled. When 
 attempting a nodetool repair on one node, i get exceptions in the other nodes 
 in the cluster.
 Disabling compression on the column family allows nodetool repair to run 
 without error.
 Exception:
 INFO [Streaming to /3.69.211.179:2] 2013-03-25 12:30:27,874 
 StreamReplyVerbHandler.java (line 50) Need to re-stream file 
 /var/lib/cassandra/data/rt/values/rt-values-ib-1-Data.db to /3.69.211.179
 INFO [Streaming to /3.69.211.179:2] 2013-03-25 12:30:27,991 
 StreamReplyVerbHandler.java (line 50) Need to re-stream file 
 /var/lib/cassandra/data/rt/values/rt-values-ib-1-Data.db to /3.69.211.179
 ERROR [Streaming to /3.69.211.179:2] 2013-03-25 12:30:28,113 
 CassandraDaemon.java (line 164) Exception in thread Thread[Streaming to 
 /3.69.211.179:2,5,main]
 java.lang.RuntimeException: java.io.EOFException
 at com.google.common.base.Throwables.propagate(Throwables.java:160)
 at 
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:32)
 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown 
 Source)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
 at java.lang.Thread.run(Unknown Source)
 Caused by: java.io.EOFException
 at java.io.DataInputStream.readInt(Unknown Source)
 at 
 org.apache.cassandra.streaming.FileStreamTask.receiveReply(FileStreamTask.java:193)
 at 
 org.apache.cassandra.streaming.compress.CompressedFileStreamTask.stream(CompressedFileStreamTask.java:114)
 at 
 org.apache.cassandra.streaming.FileStreamTask.runMayThrow(FileStreamTask.java:91)
 at 
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
 ... 3 more
 Keyspace configuration is as follows:
 Keyspace: rt:
   Replication Strategy: org.apache.cassandra.locator.SimpleStrategy
   Durable Writes: true
 Options: [replication_factor:3]
   Column Families:
 ColumnFamily: tagname
   Key Validation Class: org.apache.cassandra.db.marshal.BytesType
   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
   Populate IO Cache on flush: false
   Replicate on write: true
   Caching: KEYS_ONLY
   Bloom Filter FP chance: default
   Built indexes: []
   Compaction Strategy: 
 org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy
 ColumnFamily: values
   Key Validation Class: org.apache.cassandra.db.marshal.BytesType
   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
   Populate IO Cache on flush: false
   Replicate on write: true
   Caching: KEYS_ONLY
   Bloom Filter FP chance: default
   Built indexes: []
   Compaction Strategy: 
 org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy

--
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 QAYIanyug by QAYIanyug

Dear Wiki user,

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

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

New page:
Howdy. The author's name is Virgilio Novak and your boyfriend loves it. He once 
was unemployed but now he is often a procurement officer. Montana is where 
they're always been living.BR
To learn country music is something a he's been doing for various years. Check 
for his website here: http://www.secondarymarketannuity.net/

[jira] [Created] (CASSANDRA-5410) incremental backups race

Jonathan Ellis created CASSANDRA-5410:
-

 Summary: incremental backups race
 Key: CASSANDRA-5410
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5410
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.0.0
Reporter: Jonathan Ellis
Priority: Minor
 Fix For: 1.2.4


incremental backups does not mark things referenced or compacting, so it could 
get compacted away before createLinks runs.  Occasionally you can see this 
happen during ColumnFamilyStoreTest.  (Since it runs on the background tasks 
stage, it does not fail the test.)

{noformat}
[junit] java.lang.RuntimeException: Tried to hard link to file that does 
not exist 
build/test/cassandra/data/Keyspace1/Standard1/Keyspace1-Standard1-ja-8-Statistics.db
[junit] at 
org.apache.cassandra.io.util.FileUtils.createHardLink(FileUtils.java:72)
[junit] at 
org.apache.cassandra.io.sstable.SSTableReader.createLinks(SSTableReader.java:1066)
[junit] at 
org.apache.cassandra.db.DataTracker$1.run(DataTracker.java:168)
[junit] at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
[junit] at 
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
[junit] at java.util.concurrent.FutureTask.run(FutureTask.java:138)
[junit] at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
{noformat}

--
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-4180) Single-pass compaction for LCR

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

Jonathan Ellis commented on CASSANDRA-4180:
---

Sorry, I got caught up in this over the weekend since the more I dug on
CASSANDRA-5344 the more it looked like I was actually solving this first. I've
pushed my first draft to github.com/jbellis/cassandra/tree/4180.

I see DefsTest fail occasionally but it is not 100% reproducible, so I'm not
sure if it was caused by my changes. I also see CFSTest log errors sometimes
but that one is definitely not related (CASSANDRA-5410).

(Testing was a bitch at first since sstable errors would just cause the schema
loader to break violently; hence the option I added to just inject the schema
directly, without going through the migration path. That allowed enough tests
to run to track down the problems.)

Everything was fairly straightforward except SSTableScanner. (Sounds like the
same thing Jason ran into.) I simplified things by noting that seekTo was only
used to initialize the scanner to a certain starting point, so I pulled that
into the constructor to make seeking mid-iteration a non-concern. (This also
allowed removing SSTableBoundedScanner.) I also merged KeyScanningIterator and
FilteringKSI; FKSI already had most of the code needed to compute data size
from the index entries, which compaction needed to decide whether to use an
eager or lazy approach.

There were a lot of places that just one-off sstable reading that were easy to
miss. This smells fishy to me but it wasn't obvious how to re-organize things
to make it unnecessary, so I haven't tried to solve that here.

I also haven't tried to update scrub for the new format.

Single-pass compaction for LCR
--

Key: CASSANDRA-4180
URL: https://issues.apache.org/jira/browse/CASSANDRA-4180
Project: Cassandra
Issue Type: Improvement
Components: Core
Reporter: Sylvain Lebresne
Assignee: Jason Brown
Labels: compaction
Fix For: 2.0

LazilyCompactedRow reads all data twice to compact a row which is obviously
inefficient. The main reason we do that is to compute the row header.
However, CASSANDRA-2319 have removed the main part of that row header. What
remains is the size in bytes and the number of columns, but it should be
relatively simple to remove those, which would then remove the need for the
two-phase compaction.

--
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-4180) Single-pass compaction for LCR

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

Jonathan Ellis edited comment on CASSANDRA-4180 at 4/1/13 2:19 PM:
---

Sorry, I got caught up in this over the weekend since the more I dug on
CASSANDRA-5344 the more it looked like I was actually solving this first. I've
pushed my first draft to http://github.com/jbellis/cassandra/tree/4180.

I also haven't tried to update scrub for the new format.

was (Author: jbellis):
Sorry, I got caught up in this over the weekend since the more I dug on
CASSANDRA-5344 the more it looked like I was actually solving this first. I've
pushed my first draft to github.com/jbellis/cassandra/tree/4180.

I also haven't tried to update scrub for the new format.

Single-pass compaction for LCR
--

[Cassandra Wiki] Trivial Update of Tanesha53 by Tanesha53

Dear Wiki user,

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

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

New page:
you guild wars 2 gold   can also invest in pom pom systems in making such 
things as pets.BR
Some individuals were unsure of when it feature would stick, however it has 
been included with the game's release. For two easy points you have to buy an 
undedicated rare minipet. In Portal 2 you has a gun that shoots warp holes into 
walls, floors and ceilings. This partnership now allows credit and debit cards 
to be used at the Distributor level website. BR
BR
For instance the Monk is in fact competent to rapidly do away with several 
competitors in the area, by way of with all the way in which through the 100 
Fists capability, after that protect themself as well as their allies through 
just about all melee episodes through implementing the specific Internal Refuge 
capability. Many thanks rather certainly for that meeting. From this time on, 
your attribute allocation should be entirely in Fire Magic, Energy Storage  
Inspiration. If you cannot switch weapons, skills too monotonous. The NORTH 
AMERICAN PRE-ORDER INCLUDES:. BR
BR
According to Arena - Net on the benefit with the atmosphere. Tip 5--Dead Space 
2 Story: What's the Convergence. One of such slots is dedicated to healing 
skills that replenish the health in the character with his fantastic allies, 
while another slot is dedicated to elite skills that trigger visually 
spectacular and powerful effects.BR
No release date is scheduled to the game however it is likely to appear 
sometime mid-year. MMORPG games are getting to be in today's vast market for 
multi-player online role-playing. BR
BR
There isn't identifying characteristic to manage to tell your character is 
under Deep Wound other compared to icon. The guides will help you understand 
each with the different areas of the game. Obviously, many of us start while 
using smoothness publisher. Fun Photo Box.BR
Combat System- What makes the content scaling even more rewarding and possible, 
is the improved combat system in Guild Wars 2. BR
BR
Vengeful was Khanhei will then be used to obliterate your enemy. It may seem 
daunting, but give a few PUGs the opportunity and you will likely be surprised. 
He simultaneously also indicated that, Arena - Net opposed requests in the game 
to play the family to spend buys the force, this can create the break game 
balanced situation.BR
That's 90x5 which equals: 450. Jesus Christ.BR
BR
My web site; 
[[http://www.mimanso.net/blogs/20344/20174/quick-methods-for-guild-wars-2-g|Guild
 Wars 2 Gold]]

[Cassandra Wiki] Trivial Update of BrendaCol by BrendaCol

Dear Wiki user,

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

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

New page:
Hi! I am Andree Nishida. One of the things I take great delight in most is to 
collect kites and I'm going to never stop get moving on it. After to get out of 
all my job for time I became an accommodation receptionist. I currently live in 
Kansas. You can find my website here: http://whiteceramicwatchesforwomen.net/

[jira] [Resolved] (CASSANDRA-5408) Disabling Hinted Handoffs should stop them from being sent


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

Brandon Williams resolved CASSANDRA-5408.
-

Resolution: Duplicate

 Disabling Hinted Handoffs should stop them from being sent
 --

 Key: CASSANDRA-5408
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5408
 Project: Cassandra
  Issue Type: Improvement
Affects Versions: 1.0.11
Reporter: Matt Kapilevich

 Right now, if hinted_handoff_enabled is set to false, it stops new Hinted 
 Handoffs from being written, but the existing ones are still being sent. I 
 believe this is incorrect.
 On our cluster, we have disabled Hinted Handoffs, and a week later they are 
 still being sent to other nodes, and are still being compacted. This clearly 
 is not the desired behavior. I cannot think of a scenario when one would want 
 to keep receiving Hinted Handoffs after explicitly turning them off. By 
 turning them off, you've already stated that some data loss and inconsistency 
 is acceptable.
 A more aggressive strategy would be to remove from disk all the 
 HintsColumnFamily* files on startup, if Hinted Handoffs were turned off. This 
 would prevent them from being sent, and the existing ones from still being 
 compacted.

--
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 LeonCGBD by LeonCGBD

Dear Wiki user,

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

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

New page:
Name: Leon KochBR
Age: 24BR
Country: SwitzerlandBR
Home town: Erdesson BR
ZIP: 3979BR
Street: Fortunastrasse 72BR
BR
Feel free to surf to my web page; [[http://cotos-ever.com|oil painting]]

[jira] [Updated] (CASSANDRA-4180) Single-pass compaction for LCR


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

Jonathan Ellis updated CASSANDRA-4180:
--

Reviewer: jasobrown  (was: yukim)
Assignee: Jonathan Ellis  (was: Jason Brown)

 Single-pass compaction for LCR
 --

 Key: CASSANDRA-4180
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4180
 Project: Cassandra
  Issue Type: Improvement
  Components: Core
Reporter: Sylvain Lebresne
Assignee: Jonathan Ellis
  Labels: compaction
 Fix For: 2.0


 LazilyCompactedRow reads all data twice to compact a row which is obviously 
 inefficient. The main reason we do that is to compute the row header. 
 However, CASSANDRA-2319 have removed the main part of that row header. What 
 remains is the size in bytes and the number of columns, but it should be 
 relatively simple to remove those, which would then remove the need for the 
 two-phase compaction.

--
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-5409) Hinted Handoffs shouldn't use sstables for persistance

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

Jonathan Ellis resolved CASSANDRA-5409.
---

Resolution: Not A Problem

If you are generating so many hints that hint compaction is a major pain point,
then you need to fix whatever is causing that. In a well-run cluster, hint
generation (and hence handoff, deletion, and compaction) should be a
once-in-a-while operation. Adding a new storage format would thus be a bad
investment.

Hinted Handoffs shouldn't use sstables for persistance
--

Key: CASSANDRA-5409
URL: https://issues.apache.org/jira/browse/CASSANDRA-5409
Project: Cassandra
Issue Type: Improvement
Affects Versions: 1.0.11
Reporter: Matt Kapilevich

I'm questioning the design decision to use sstables for storing Hinted
Handoffs.
sstables are optimized for reads. Things like bloom-filters, indexes, and the
like - none of these are necessary for Hinted Handoffs.
After turning off Hinted Handoffs, I'm still seeing Hinted Handoffs be
compacted a week later. The fact that they are compacted in the first place
doesn't seem right. The whole purpose of compaction is to optimize sstables
for reads, which doesn't apply here.
In our case, this is exacerbated by using Leveled Compaction. The overhead of
compactions is significantly larger with LCS. When compactions begin to
backup under heavy write load, Hinted Handoffs contribute to that.
Another thing that makes it worse (I think) is that Hinted Handoffs are
stored on Coordinator nodes after 1.0. That means that these are being
compacted across all key-ranges.
It seems that Hinted Handoffs should be persisted in a simple queue-like
data-structure, that's not sorted by keys. The only thing the data-structure
needs to support is the ability to replay them in order.
A simpler improvement would be to introduce max_hint_window_size_in_mb
property, in addition to max_hint_window_in_ms. That would at least allow you
to control how much these build up.

[1/3] git commit: clean up string concatenation in logging

Updated Branches:
  refs/heads/cassandra-1.2 c96cce9ee - 5b157e476
  refs/heads/trunk 9f8526fef - d3921d637


clean up string concatenation in logging


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

Branch: refs/heads/cassandra-1.2
Commit: 5b157e47695dd5cb656d9354ed8a00033e22e9e8
Parents: c96cce9
Author: Jonathan Ellis jbel...@apache.org
Authored: Tue Mar 26 16:49:02 2013 -0500
Committer: Jonathan Ellis jbel...@apache.org
Committed: Mon Apr 1 10:45:20 2013 -0500

--
 .../org/apache/cassandra/transport/Message.java|4 ++--
 .../org/apache/cassandra/transport/Server.java |4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/5b157e47/src/java/org/apache/cassandra/transport/Message.java
--
diff --git a/src/java/org/apache/cassandra/transport/Message.java 
b/src/java/org/apache/cassandra/transport/Message.java
index 8aec501..5cc3998 100644
--- a/src/java/org/apache/cassandra/transport/Message.java
+++ b/src/java/org/apache/cassandra/transport/Message.java
@@ -282,14 +282,14 @@ public abstract class Message
 ServerConnection connection = 
(ServerConnection)request.connection();
 connection.validateNewMessage(request.type);
 
-logger.debug(Received:  + request);
+logger.debug(Received: {}, request);
 
 Response response = 
request.execute(connection.getQueryState(request.getStreamId()));
 response.setStreamId(request.getStreamId());
 response.attach(connection);
 connection.applyStateTransition(request.type, response.type);
 
-logger.debug(Responding:  + response);
+logger.debug(Responding: {}, response);
 
 ctx.getChannel().write(response);
 }

http://git-wip-us.apache.org/repos/asf/cassandra/blob/5b157e47/src/java/org/apache/cassandra/transport/Server.java
--
diff --git a/src/java/org/apache/cassandra/transport/Server.java 
b/src/java/org/apache/cassandra/transport/Server.java
index 68160c6..0b01c0d 100644
--- a/src/java/org/apache/cassandra/transport/Server.java
+++ b/src/java/org/apache/cassandra/transport/Server.java
@@ -132,7 +132,7 @@ public class Server implements CassandraDaemon.Server
 }
 
 // Bind and start to accept incoming connections.
-logger.info(Starting listening for CQL clients on  + socket + ...);
+logger.info(Starting listening for CQL clients on {}..., socket);
 Channel channel = bootstrap.bind(socket);
 connectionTracker.allChannels.add(channel);
 }
@@ -292,7 +292,7 @@ public class Server implements CassandraDaemon.Server
 {
 // That should not happen, so log an error, but return the
 // endpoint address since there's a good change this is right
-logger.error(Problem retrieving RPC address for  + endpoint, 
e);
+logger.error(Problem retrieving RPC address for {}, 
endpoint, e);
 return endpoint;
 }
 }

[3/3] 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/d3921d63
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/d3921d63
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/d3921d63

Branch: refs/heads/trunk
Commit: d3921d6379bc3035558a8b572ca3703e33249925
Parents: 9f8526f 5b157e4
Author: Jonathan Ellis jbel...@apache.org
Authored: Mon Apr 1 10:45:54 2013 -0500
Committer: Jonathan Ellis jbel...@apache.org
Committed: Mon Apr 1 10:45:54 2013 -0500

--
 .../org/apache/cassandra/transport/Server.java |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
--

[2/3] git commit: clean up string concatenation in logging

clean up string concatenation in logging


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

Branch: refs/heads/trunk
Commit: 5b157e47695dd5cb656d9354ed8a00033e22e9e8
Parents: c96cce9
Author: Jonathan Ellis jbel...@apache.org
Authored: Tue Mar 26 16:49:02 2013 -0500
Committer: Jonathan Ellis jbel...@apache.org
Committed: Mon Apr 1 10:45:20 2013 -0500

--
 .../org/apache/cassandra/transport/Message.java|4 ++--
 .../org/apache/cassandra/transport/Server.java |4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/5b157e47/src/java/org/apache/cassandra/transport/Message.java
--
diff --git a/src/java/org/apache/cassandra/transport/Message.java 
b/src/java/org/apache/cassandra/transport/Message.java
index 8aec501..5cc3998 100644
--- a/src/java/org/apache/cassandra/transport/Message.java
+++ b/src/java/org/apache/cassandra/transport/Message.java
@@ -282,14 +282,14 @@ public abstract class Message
 ServerConnection connection = 
(ServerConnection)request.connection();
 connection.validateNewMessage(request.type);
 
-logger.debug(Received:  + request);
+logger.debug(Received: {}, request);
 
 Response response = 
request.execute(connection.getQueryState(request.getStreamId()));
 response.setStreamId(request.getStreamId());
 response.attach(connection);
 connection.applyStateTransition(request.type, response.type);
 
-logger.debug(Responding:  + response);
+logger.debug(Responding: {}, response);
 
 ctx.getChannel().write(response);
 }

http://git-wip-us.apache.org/repos/asf/cassandra/blob/5b157e47/src/java/org/apache/cassandra/transport/Server.java
--
diff --git a/src/java/org/apache/cassandra/transport/Server.java 
b/src/java/org/apache/cassandra/transport/Server.java
index 68160c6..0b01c0d 100644
--- a/src/java/org/apache/cassandra/transport/Server.java
+++ b/src/java/org/apache/cassandra/transport/Server.java
@@ -132,7 +132,7 @@ public class Server implements CassandraDaemon.Server
 }
 
 // Bind and start to accept incoming connections.
-logger.info(Starting listening for CQL clients on  + socket + ...);
+logger.info(Starting listening for CQL clients on {}..., socket);
 Channel channel = bootstrap.bind(socket);
 connectionTracker.allChannels.add(channel);
 }
@@ -292,7 +292,7 @@ public class Server implements CassandraDaemon.Server
 {
 // That should not happen, so log an error, but return the
 // endpoint address since there's a good change this is right
-logger.error(Problem retrieving RPC address for  + endpoint, 
e);
+logger.error(Problem retrieving RPC address for {}, 
endpoint, e);
 return endpoint;
 }
 }

[Cassandra Wiki] Trivial Update of HenryScul by HenryScul

Dear Wiki user,

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

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

New page:
brBeneath the have these 5 which will help you in the deal.BR
You have to lenders would inquire of or check with respect to reviewing the 
application will be fico. You actually may know that you've adverse credit 
rating but ever taken serious amounts of read why thats generally? So some tips 
about what to perform: Get erroneous information to your credit rating removed. 
Inaccurate data concerning your credit behavior within your credit score can 
give down your credit score. Acquire credit due to the fact you might discover 
inaccurate entries, inform that credit reference agency and  written. 
brbrBR
BR
poor credit loans -- Certain KnowledgeBR
BR
brIt grades them A to F, depending on amount complaints made on them. Only 
select a grade A lender, then examine the details in it of your deals. Often 
hidden charges and conditions are revealed there, so it is here that your value 
of any unsecured loans is proven. There are lots of families would you care to 
own their private home avoiding from the troubles that feature renting. 
However, that thought this indicates an impossible achievement as the credit 
history is poor. brbrBR
BR
brYou can receive many sub-prime lenders with the aid internet. There are 
many online car financing businesses that have huge network of sub-prime 
lenders. Incorporating do is search for a reputed car bank and apply on its 
website to get a an unfavorable credit rating a car loan. Any time you apply by 
submitting an internet based car loan application form, company will search a 
lender for you.[[http://www.unsecuredbadcreditloans.co.uk/|bad credit loans]] 
At the time you apply with internet sub-prime lenders, you may several an 
unfavorable credit rating auto loan financing quotes. Now, correct moment to 
prefer a quality choice for you.brBR
brBR
brIt signifies there won't be any disappearance of your credit ratings . in 
the event you request motor loans with terrible credit history. So, depart 
there and try for auto financing absolutely no worry. The typical advice, their 
own with less-than-perfect credit, usually never borrow until credit 
improves.BR
However, occasionally a great loans will assist to people get high interest 
loans settled, and may even certainly step towards regaining a good credit 
record. The difficulty with using a lower interest loans, is the most lenders 
only reserve those for people with really good credit histories.BR
br

git commit: generify

Updated Branches:
  refs/heads/trunk d3921d637 - 1d3ad3047


generify


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

Branch: refs/heads/trunk
Commit: 1d3ad3047ed04b5810f9896acdffcf55f2d9d5e3
Parents: d3921d6
Author: Jonathan Ellis jbel...@apache.org
Authored: Wed Mar 27 11:58:11 2013 -0500
Committer: Jonathan Ellis jbel...@apache.org
Committed: Mon Apr 1 11:11:05 2013 -0500

--
 .../db/index/composites/CompositesSearcher.java|2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/1d3ad304/src/java/org/apache/cassandra/db/index/composites/CompositesSearcher.java
--
diff --git 
a/src/java/org/apache/cassandra/db/index/composites/CompositesSearcher.java 
b/src/java/org/apache/cassandra/db/index/composites/CompositesSearcher.java
index 1f201db..a333000 100644
--- a/src/java/org/apache/cassandra/db/index/composites/CompositesSearcher.java
+++ b/src/java/org/apache/cassandra/db/index/composites/CompositesSearcher.java
@@ -228,7 +228,7 @@ public class CompositesSearcher extends 
SecondaryIndexSearcher
 
 CollectionColumn sortedColumns = 
indexRow.getSortedColumns();
 columnsRead = sortedColumns.size();
-indexColumns = new ArrayDeque(sortedColumns);
+indexColumns = new ArrayDequeColumn(sortedColumns);
 Column firstColumn = sortedColumns.iterator().next();
 
 // Paging is racy, so it is possible the first column 
of a page is not the last seen one.

[jira] [Commented] (CASSANDRA-5403) Clean up ColumnFamily, ISortedColumns heirarchy


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

Jonathan Ellis commented on CASSANDRA-5403:
---

Rebased on top of trunk (post-5395-commit) and fixed some test errors: 
https://github.com/jbellis/cassandra/tree/5403-2

 Clean up ColumnFamily, ISortedColumns heirarchy
 ---

 Key: CASSANDRA-5403
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5403
 Project: Cassandra
  Issue Type: Bug
Reporter: Jonathan Ellis
Assignee: Jonathan Ellis
 Fix For: 2.0


 CF wraps ISC but adds no real functionality of its own (post-supercolumn 
 cleanup).
 This means that we're wasting allocations every time we create a CF/ISC pair 
 when really one would do.
 Other things that would be nice to clean up:
 # We often create an empty CF as a placeholder that should not be modified, 
 and rely on convention to avoid such modification.  We could enforce this 
 with a new CF/ISC subclass.
 # Many places still use TMBSC where ABSC would be adequate and cheaper
 # Other places still (ModificationStatement; others?) would be fine using a 
 column container with no sorting requirement at all

--
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-5403) Clean up ColumnFamily, ISortedColumns heirarchy


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

Jonathan Ellis edited comment on CASSANDRA-5403 at 4/1/13 4:19 PM:
---

Rebased on top of trunk (post-5395-commit) and fixed some test errors: 
https://github.com/jbellis/cassandra/commits/5403-2

  was (Author: jbellis):
Rebased on top of trunk (post-5395-commit) and fixed some test errors: 
https://github.com/jbellis/cassandra/tree/5403-2
  
 Clean up ColumnFamily, ISortedColumns heirarchy
 ---

 Key: CASSANDRA-5403
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5403
 Project: Cassandra
  Issue Type: Bug
Reporter: Jonathan Ellis
Assignee: Jonathan Ellis
 Fix For: 2.0


 CF wraps ISC but adds no real functionality of its own (post-supercolumn 
 cleanup).
 This means that we're wasting allocations every time we create a CF/ISC pair 
 when really one would do.
 Other things that would be nice to clean up:
 # We often create an empty CF as a placeholder that should not be modified, 
 and rely on convention to avoid such modification.  We could enforce this 
 with a new CF/ISC subclass.
 # Many places still use TMBSC where ABSC would be adequate and cheaper
 # Other places still (ModificationStatement; others?) would be fine using a 
 column container with no sorting requirement at all

--
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 LetaEscam by LetaEscam

Dear Wiki user,

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

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

New page:
Permit me to inroduce myself, my name are Breann. For years Web site been 
working as an invoicing officer and I'll be advertised soon. One of the very 
best information in the world for people is playing handball and I will be 
starting something else along utilizing. Hawaii is the only place I've found 
itself residing in.BR
I've been working on my net site for some time now. Give it a look here: 
http://www.portcontainers.com

[Cassandra Wiki] Trivial Update of BarbWhite by BarbWhite

Dear Wiki user,

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

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

New page:
Royce is what you can contact us him and he believes information technology 
sounds quite good.BR
He's always loved living in Mo and he loves every work day living there. 
Booking holidays is just how he supports his family. His partners say it's not 
good with respect to him but what he take interest in doing is body building 
despite the fact that he can't make it his / her profession. Check out the 
state-of-the-art news on his website: http://www.palmfanstore.com

[Cassandra Wiki] Trivial Update of TimofAdam by TimofAdam

Dear Wiki user,

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

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

New page:
Got nothing to say about myself really.BR
Nice to be here and a part of this community.BR
I really wish Im useful in one way .BR
BR
my page 
[[http://sns.cam111.com/blogs/entry/Rapid-Products-For-airport-parking-Clarified|just
 click the following web site]]

[jira] [Commented] (CASSANDRA-5403) Clean up ColumnFamily, ISortedColumns heirarchy


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

Jonathan Ellis commented on CASSANDRA-5403:
---

According to YourKit, this takes the time in CF.addColumn from 50% of 
mutationsForKey to 10%.

 Clean up ColumnFamily, ISortedColumns heirarchy
 ---

 Key: CASSANDRA-5403
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5403
 Project: Cassandra
  Issue Type: Bug
Reporter: Jonathan Ellis
Assignee: Jonathan Ellis
 Fix For: 2.0


 CF wraps ISC but adds no real functionality of its own (post-supercolumn 
 cleanup).
 This means that we're wasting allocations every time we create a CF/ISC pair 
 when really one would do.
 Other things that would be nice to clean up:
 # We often create an empty CF as a placeholder that should not be modified, 
 and rely on convention to avoid such modification.  We could enforce this 
 with a new CF/ISC subclass.
 # Many places still use TMBSC where ABSC would be adequate and cheaper
 # Other places still (ModificationStatement; others?) would be fine using a 
 column container with no sorting requirement at all

--
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-5403) Clean up ColumnFamily, ISortedColumns heirarchy


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

Jonathan Ellis updated CASSANDRA-5403:
--

Attachment: Screen Shot 2013-04-01 at 12.00.09 PM.png

Most of the rest of the time is taken up by CompositeType construction. :-|

 Clean up ColumnFamily, ISortedColumns heirarchy
 ---

 Key: CASSANDRA-5403
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5403
 Project: Cassandra
  Issue Type: Bug
Reporter: Jonathan Ellis
Assignee: Jonathan Ellis
 Fix For: 2.0

 Attachments: Screen Shot 2013-04-01 at 12.00.09 PM.png


 CF wraps ISC but adds no real functionality of its own (post-supercolumn 
 cleanup).
 This means that we're wasting allocations every time we create a CF/ISC pair 
 when really one would do.
 Other things that would be nice to clean up:
 # We often create an empty CF as a placeholder that should not be modified, 
 and rely on convention to avoid such modification.  We could enforce this 
 with a new CF/ISC subclass.
 # Many places still use TMBSC where ABSC would be adequate and cheaper
 # Other places still (ModificationStatement; others?) would be fine using a 
 column container with no sorting requirement at all

--
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-4932) Agree on a gcbefore/expirebefore value for all replica during validation compaction


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

Jonathan Ellis updated CASSANDRA-4932:
--

Reviewer: yukim

 Agree on a gcbefore/expirebefore value for all replica during validation 
 compaction 
 

 Key: CASSANDRA-4932
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4932
 Project: Cassandra
  Issue Type: Improvement
Reporter: Sylvain Lebresne
Assignee: Marcus Eriksson
Priority: Minor
 Fix For: 2.0

 Attachments: 0001-CASSANDRA-4932.patch


 CASSANDRA-4905 made it so that we don't include gcable tombstones in merkle 
 tree digests because otherwise the fact that a gcable tombstone exists in a 
 given node depends on the local scheduling of compactions, which make the 
 merkle-tree digets depends on that which is bad.
 However, we still depends on a value of gcbefore/expirebefore that is 
 computed locally on the node. This is not a huge deal because each node 
 should compute those value roughly at the same time so the discrepancies 
 shouldn't exceed a few hundreds of milliseconds in general and a few seconds 
 if we're unlucky. Still, it's fairly easy to fix this problem by having the 
 repair coordinator pick the gcbefore/expirebefore and share that with all the 
 replica. It does require sending that info on the wire though, so will 
 require a new messaging version and thus can only be done in a major cycle. 

--
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-5407) Repair exception when getPositionsForRanges returns empty iterator


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

Jonathan Ellis commented on CASSANDRA-5407:
---

What is causing the breakage?  Is it possible to add a test that exposes the 
problem?

 Repair exception when getPositionsForRanges returns empty iterator
 --

 Key: CASSANDRA-5407
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5407
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 2.0
Reporter: Marcus Eriksson
Assignee: Marcus Eriksson
 Attachments: 
 0001-Fix-repair-bug-where-getPositionsForRanges-returns-e.patch


 CASSANDRA-5250 broke repair, this re-adds the code from CASSANDRA-5249

--
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-4510) cassandra block request when it is soon OOM


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

Jonathan Ellis resolved CASSANDRA-4510.
---

Resolution: Won't Fix

Cassandra does its best to free up memory when the heap is extra full, but 
shutting down thrift doesn't help much since it can receive requests from other 
cluster members.  (And if we were to shut down both, we might as well just kill 
the process...)

 cassandra block request when it is soon OOM
 ---

 Key: CASSANDRA-4510
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4510
 Project: Cassandra
  Issue Type: New Feature
Affects Versions: 1.1.3
 Environment: Debian squeeze 32bit
Reporter: Tommy Cheng
  Labels: compact, heap, hector, oom

 I have 256MB memory Debian to do the stress test (it is easier to find out 
 the problem)
 This is my setting excepts the default
 MAX_HEAP_SIZE=192M
 HEAP_NEWSIZE=16M
 commitlog_segment_size_in_mb: 4
 flush_largest_memtables_at: 0.5 (too few memory, flush it earlier...)
 concurrent_reads: 16
 concurrent_writes: 8
 memtable_total_space_in_mb: 64
 commitlog_total_space_in_mb: 4
 memtable_flush_queue_size: 6
 in_memory_compaction_limit_in_mb: 4
 concurrent_compactors: 1
 stream_throughput_outbound_megabits_per_sec: 400
 rpc_timeout_in_ms: 6
 And this is my schema
 create keyspace PT
 with placement_strategy = 'org.apache.cassandra.locator.SimpleStrategy'
 and strategy_options = [{replication_factor:1}];
 use PT;
 create column family cheque
 with comparator = UTF8Type 
 and key_validation_class = UTF8Type
 and default_validation_class = UTF8Type
 and column_metadata = [
 {column_name: acct_no, validation_class: UTF8Type, 
 index_name:cheque_acct_no_idx, index_type:KEYS } {column_name: date, 
 validation_class: UTF8Type, index_name:cheque_date_idx, index_type:KEYS } 
 {column_name: bank, validation_class: UTF8Type, index_name:cheque_bank_idx, 
 index_type:KEYS } {column_name: amount, validation_class: LongType, 
 index_name:cheque_amout_idx, index_type:KEYS } {column_name: receipt, 
 validation_class: UTF8Type, index_name:cheque_receipt_idx, index_type:KEYS }  
  {column_name: create_timestamp, validation_class: LongType, 
 index_name:cheque_create_timestamp_idx, index_type:KEYS} {column_name: image, 
 validation_class: BytesType}
 ];
 I tried to insert a 50KB file per record using hector 1.1.0
 I did not set any swap as it is not recommended.
 GC is working and telling me 0.80 heap is used, blahblahblah, the number 
 finally reach 0.99 and of course OOM happens
 So my question is the following
 Can the server block the incoming insert when the heap size used is 0.95, is 
 it feasible?
 I know hector will retry when timeoutexception happens. so it is good to 
 implement blocking features instead of throttling in client problem.
 Sorry for my poor english and i am completely cassandra newbie, so my wish 
 may not valid.
 Thanks!

--
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-5392) cassandra-all 1.2.0 pom missing netty dependency


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

Jonathan Ellis updated CASSANDRA-5392:
--

Reviewer: dbrosius
Assignee: Sean Bridges

 cassandra-all 1.2.0 pom missing netty dependency
 

 Key: CASSANDRA-5392
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5392
 Project: Cassandra
  Issue Type: Bug
  Components: Packaging
Affects Versions: 1.2.3
Reporter: Sean Bridges
Assignee: Sean Bridges
 Fix For: 1.2.4

 Attachments: CASSANDRA-5392.txt


 It seems that cassandra depends on netty now, however the pom excludes this 
 dependency.  This was previously reported as CASSANDRA-5181, but the fix for 
 5181 added netty to the dependency-management section of the pom, not the 
 depencies section

--
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-5397) Updates to PerRowSecondaryIndex don't use most current values


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

Jonathan Ellis commented on CASSANDRA-5397:
---

TBH my preferred fix here would be to make PerRowSI also do lazy updates a la 
CASSANDRA-2897.  Is that possible?

 Updates to PerRowSecondaryIndex don't use most current values 
 --

 Key: CASSANDRA-5397
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5397
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.2.3
Reporter: Sam Tunnicliffe
Assignee: Sam Tunnicliffe
Priority: Minor
 Attachments: 5397.txt


 The way that updates to secondary indexes are performed using  
 SecondaryIndexManager.Updater is flawed for PerRowSecondaryIndexes.  Unlike 
 PerColumnSecondaryIndexes, which only require the old  new values for a 
 single column,  the expectation is that a PerRow indexer can be given just a 
 key which it will use to retrieve the entire row (or as many columns as it 
 requires) and perform its indexing on those columns.  As the indexes are 
 updated before the memtable atomic swap occurs, a per-row indexer may only 
 read the previous values for the row, not the new ones that are being 
 written. In the case of an insert, there is no previous value and so nothing 
 is added to 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-5407) Repair exception when getPositionsForRanges returns empty iterator

2013-04-01 Thread Marcus Eriksson (JIRA)


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

Marcus Eriksson commented on CASSANDRA-5407:


my fix in CASSANDRA-5250 just fixed it for LCS (tests if intersecting sstables 
is empty in LeveledScanner), and this re-broke it for STCS

i'll try to write a unit test for this

 Repair exception when getPositionsForRanges returns empty iterator
 --

 Key: CASSANDRA-5407
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5407
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 2.0
Reporter: Marcus Eriksson
Assignee: Marcus Eriksson
 Attachments: 
 0001-Fix-repair-bug-where-getPositionsForRanges-returns-e.patch


 CASSANDRA-5250 broke repair, this re-adds the code from CASSANDRA-5249

--
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 DanielleL by DanielleL

Dear Wiki user,

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

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

New page:
This could be a great tool to express photos with the rest of the network or 
distant relatives.BR
BR
This will be the very best free host ever. It remains web hosting however, you 
only reach pay once - no regular debts - this is exactly why it's called 
lifetime. for you:. After owning a Word - Press blog for a number of months or 
even years, you may discover that it has outgrown its original hosting package 
and is also ready to get a new home. BR
BR
Net. As a blogger, it's easier to link a picture straight out of your photo 
album versus pulling urls from another webhosting site. Word - Press Database 
Backup Plugin:. So being a business owner you need to to talk about certain 
features your small business really needs as well as have to overlook the 
relaxation altogether.BR
5Gb of disk or web space. BR
BR
The use of a control panel will determine how we would like your server to 
operate. As the consumer has several resources available with him, he's got the 
capability to expand the business enterprise without having to incur any extra 
costs. Memory ' Go no less than 512 MB.BR
This demonstration of Dream - Host's customer support really paints a 
definative picture of how responsive they may be to their customers needs. 
Technology itself provides solution. BR
BR
The small enterprise have gladly accepted the advantages that cloud hosting 
services have bestowed with regards to always on application access, 
collaborative platform above all cost benefits and reorganization of business 
priorities that it's affected. Be sure to find one that does exactly that.BR
With environmental issues engaging the serious attention of business houses 
across the world, a whole new technology has become evolved to offer all 
webmasters to either rent or purchase green hosting. Downloads that employed to 
take hrs to complete can now be done in a very couple of minutes.BR
95. BR
BR
The whole process is called web site hosting or perhaps hosting. Everyone has 
their own preferred tax application to achieve their tax return jobs 
nevertheless the usage method can play an incredibly important role towards the 
job quality and completion time. Waw is fantastic, it wasn't just the name 
alone Inde - Host Good and Cheap Web Hosting Indonesia but also the fact that 
there is really a Service Provider that Inde - Host Web Hosting Bagus dan Murah 
Indonesia. Third and last could be the control panel what type of control panel 
you require for editing. ), CGI, Database (including: My - SQL, Microsoft SQL, 
etc.BR
BR
My blog [[http://korillolatino.com/profile-17739/info/|jaipur web hosting 
company]]

[Cassandra Wiki] Trivial Update of Evaarmoxm by Evaarmoxm

Dear Wiki user,

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

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

New page:
She went original provider of your service may consider this a follow up 
cosmetics with an established client.BR
BR
BR
Here is my web site: 
[[http://geekmotion.com/index.php?do=/profile-28004/info/|Http://Geekmotion.Com/Index.Php?Do=/Profile-28004/Info]]

git commit: add netty.jar as a dependency for all-pom patch by sbridges reviewed by dbrosius

Updated Branches:
  refs/heads/cassandra-1.2 5b157e476 - e06875ed2


add netty.jar as a dependency for all-pom
patch by sbridges reviewed by dbrosius


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

Branch: refs/heads/cassandra-1.2
Commit: e06875ed2cd47f7bd77eaae9cc70dee5a3c0371a
Parents: 5b157e4
Author: Dave Brosius dbros...@apache.org
Authored: Mon Apr 1 14:53:24 2013 -0400
Committer: Dave Brosius dbros...@apache.org
Committed: Mon Apr 1 14:53:24 2013 -0400

--
 build.xml |1 +
 1 files changed, 1 insertions(+), 0 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/e06875ed/build.xml
--
diff --git a/build.xml b/build.xml
index 1d1bb7c..a57d669 100644
--- a/build.xml
+++ b/build.xml
@@ -482,6 +482,7 @@
 
 !-- don't need jamm unless running a server in which case it needs to 
be a -javagent to be used anyway --
 dependency groupId=com.github.stephenc artifactId=jamm/
+dependency groupId=io.netty artifactId=netty/
   /artifact:pom
   artifact:pom id=thrift-pom
 artifactId=cassandra-thrift

[Cassandra Wiki] Trivial Update of LavadaSon by LavadaSon

Dear Wiki user,

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

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

New page:
They're awesome, but when you are much like me, you wonder if you happen to be 
doing the exercises correctly or if you are doing it while using proper form. I 
have organized baskets by forms of toys: cars, trains, play food, blocks, 
Legos, etc. Listed involving Rs 995-1, 950, the girl selection supplies the 
actual brand-new worldwide 'Frosted' appear, which is fashionable and also 
fashionable. Game Over. You might want to consider the watch off your wrist to 
get the most accurate temperature readings however. BR
BR
When using multiple squads, all squads are shuffled right into a single deck 
and both opponents have higher starting morale totals, depending around the 
exact number of squads used. ) then this HTC Freestyle will be the wrong phone 
to purchase. Believe me, this is really a dream killer. The gadget permits you 
to select location and date then gives you a thorough weather forecast for the 
said location. As you progress over the game, the hearts will fall in ways. 
BR
BR
You can put '300' seconds as this would be 5 minutes. Unfortunately the handset 
won't have an MP3 player; although it comes having an FM radio feature that 
permits you to preset up to 20 stations.BR
The LCD screen will even show a countdown so you know exactly whenever your 
toast will be ready. In short -- it is a well-made app. Well, that's just what 
Ribbit offers. BR
BR
For example, suppose someone refuses to play and is also standing on the 
fountain so you report him as afk. com offers a solution for the problem of 
overrun agendas with its next up timer. Completing later levels may have the 
player's reflexes and problem solving skills tested simultaneously.BR
If our time is short, their preparation time is a minute along with their 
speech is three minutes. ' When you find the driving force to download, the web 
site will provide you with instructions regarding how to install it. BR
BR
print My birthday will start in $days hours;. Instead of deciding on how to 
use your cards during each turn with the game, a certain AI controls how cards 
act on each turn, for both sides of the game. It looks like the person in 
charge with the Freestyle's set of features would be a bit confused in regards 
to the finer points of international network frequencies.BR
Keep in your mind that this can be a powerful marketing device that in the 
event you choose to use it properly, will help boost the overall sales on your 
website. Contract phone deal is preferable since it includes stunning free 
gifts and incentives including free texts, free minutes and instant cash back 
offers etc.BR
BR
BR
My weblog: 
[[http://hook2it.com/blogs/entry/No-Hassle-Products-Of-Online-Timer-Clarified|countdown
 timer]]

[jira] [Commented] (CASSANDRA-5392) cassandra-all 1.2.0 pom missing netty dependency

2013-04-01 Thread Dave Brosius (JIRA)


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

Dave Brosius commented on CASSANDRA-5392:
-

+1, committed to cassandra-1.2 as e06875ed2cd47f7bd77eaae9cc70dee5a3c0371a

 cassandra-all 1.2.0 pom missing netty dependency
 

 Key: CASSANDRA-5392
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5392
 Project: Cassandra
  Issue Type: Bug
  Components: Packaging
Affects Versions: 1.2.3
Reporter: Sean Bridges
Assignee: Sean Bridges
 Fix For: 1.2.4

 Attachments: CASSANDRA-5392.txt


 It seems that cassandra depends on netty now, however the pom excludes this 
 dependency.  This was previously reported as CASSANDRA-5181, but the fix for 
 5181 added netty to the dependency-management section of the pom, not the 
 depencies section

--
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

git commit: add #5392 to changes.txt

Updated Branches:
  refs/heads/cassandra-1.2 e06875ed2 - 50aa1f707


add #5392 to changes.txt


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

Branch: refs/heads/cassandra-1.2
Commit: 50aa1f707ca8ca1581cd1dcae914f89b55bbc3f6
Parents: e06875e
Author: Dave Brosius dbros...@apache.org
Authored: Mon Apr 1 14:59:35 2013 -0400
Committer: Dave Brosius dbros...@apache.org
Committed: Mon Apr 1 14:59:35 2013 -0400

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


http://git-wip-us.apache.org/repos/asf/cassandra/blob/50aa1f70/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index dafb9a8..ca062d6 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -14,6 +14,7 @@
  * Copy resultSet on count query to avoid ConcurrentModificationException 
(CASSANDRA-5382)
  * Correctly typecheck in CQL3 even with ReversedType (CASSANDRA-5386)
  * Fix streaming compressed files when using encryption (CASSANDRA-5391)
+ * cassandra-all 1.2.0 pom missing netty dependency (CASSANDRA-5392)
 Merged from 1.1:
  * cli: Quote ks and cf names in schema output when needed (CASSANDRA-5052)
  * Fix bad default for min/max timestamp in SSTableMetadata (CASSANDRA-5372)

[1/3] git commit: add netty.jar as a dependency for all-pom patch by sbridges reviewed by dbrosius

Updated Branches:
  refs/heads/trunk 1d3ad3047 - b7398


add netty.jar as a dependency for all-pom
patch by sbridges reviewed by dbrosius


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

Branch: refs/heads/trunk
Commit: e06875ed2cd47f7bd77eaae9cc70dee5a3c0371a
Parents: 5b157e4
Author: Dave Brosius dbros...@apache.org
Authored: Mon Apr 1 14:53:24 2013 -0400
Committer: Dave Brosius dbros...@apache.org
Committed: Mon Apr 1 14:53:24 2013 -0400

--
 build.xml |1 +
 1 files changed, 1 insertions(+), 0 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/e06875ed/build.xml
--
diff --git a/build.xml b/build.xml
index 1d1bb7c..a57d669 100644
--- a/build.xml
+++ b/build.xml
@@ -482,6 +482,7 @@
 
 !-- don't need jamm unless running a server in which case it needs to 
be a -javagent to be used anyway --
 dependency groupId=com.github.stephenc artifactId=jamm/
+dependency groupId=io.netty artifactId=netty/
   /artifact:pom
   artifact:pom id=thrift-pom
 artifactId=cassandra-thrift

[2/3] git commit: add #5392 to changes.txt

add #5392 to changes.txt


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

Branch: refs/heads/trunk
Commit: 50aa1f707ca8ca1581cd1dcae914f89b55bbc3f6
Parents: e06875e
Author: Dave Brosius dbros...@apache.org
Authored: Mon Apr 1 14:59:35 2013 -0400
Committer: Dave Brosius dbros...@apache.org
Committed: Mon Apr 1 14:59:35 2013 -0400

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


http://git-wip-us.apache.org/repos/asf/cassandra/blob/50aa1f70/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index dafb9a8..ca062d6 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -14,6 +14,7 @@
  * Copy resultSet on count query to avoid ConcurrentModificationException 
(CASSANDRA-5382)
  * Correctly typecheck in CQL3 even with ReversedType (CASSANDRA-5386)
  * Fix streaming compressed files when using encryption (CASSANDRA-5391)
+ * cassandra-all 1.2.0 pom missing netty dependency (CASSANDRA-5392)
 Merged from 1.1:
  * cli: Quote ks and cf names in schema output when needed (CASSANDRA-5052)
  * Fix bad default for min/max timestamp in SSTableMetadata (CASSANDRA-5372)

[Cassandra Wiki] Trivial Update of Brady0226 by Brady0226

Dear Wiki user,

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

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

New page:
My name: Brady McgeheeBR
Age: 34BR
Country: AustriaBR
City: Hart Bei Graz BR
ZIP: 8047BR
Address: Grazer Strasse 63BR
BR
my web page; [[http://retractablebannerstands.tumblr.com/|visit the following 
post]]

[jira] [Commented] (CASSANDRA-5401) Pluggable security feature to prevent node from joining a cluster and running destructive commands


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

Brandon Williams commented on CASSANDRA-5401:
-

To clarify, what we want here is a pluggable way to authenticate nodes that are 
trying to join the cluster (in any way, I don't mean just bootstrapping.)  SSL 
can do this, but maintaining a full CA and dealing with certificate expiration 
is cumbersome, plus encryption carries some overhead, so it's kind of an 
all-or-nothing solution.  Instead, I think we can create some kind of interface 
for this and ship our own 'allow all' implementation of it, with a simple hook 
into ITC to allow/disallow connections at the TCP level, and anyone wanting to 
do this can provide their own implementation.  The hardest part is going to be 
coming up with names for all these things that aren't already used for client 
authentication.

 Pluggable security feature to prevent node from joining a cluster and running 
 destructive commands
 --

 Key: CASSANDRA-5401
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5401
 Project: Cassandra
  Issue Type: Improvement
  Components: Config, Core
Affects Versions: 1.1.10
 Environment: Production
Reporter: Ahmed Bashir
  Labels: configuration, security

 It's possible for a node to join an existing cluster (with perhaps more 
 stringent security restrictions i.e. not using AllowAllAuthentication) and 
 issue destructive commands that affect the cluster at large (e.g. drop 
 keyspace via cassandra-cli, etc).  
 This can be circumvented with a pluggable security module that could be used 
 to implement basic node vetting/identification/etc.  

--
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-5401) Pluggable security feature to prevent node from joining a cluster and running destructive commands


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

Brandon Williams reassigned CASSANDRA-5401:
---

Assignee: Aleksey Yeschenko

 Pluggable security feature to prevent node from joining a cluster and running 
 destructive commands
 --

 Key: CASSANDRA-5401
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5401
 Project: Cassandra
  Issue Type: Improvement
  Components: Config, Core
Affects Versions: 1.1.10
 Environment: Production
Reporter: Ahmed Bashir
Assignee: Aleksey Yeschenko
  Labels: configuration, security

 It's possible for a node to join an existing cluster (with perhaps more 
 stringent security restrictions i.e. not using AllowAllAuthentication) and 
 issue destructive commands that affect the cluster at large (e.g. drop 
 keyspace via cassandra-cli, etc).  
 This can be circumvented with a pluggable security module that could be used 
 to implement basic node vetting/identification/etc.  

--
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 MelisaThm by MelisaThm

Dear Wiki user,

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

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

New page:
He is known by selected of Scot Hughley. Georgia is where he's been having 
lived for years. Managing everyone is his careers. He is amazingly fond of cats 
but he's philosophy on starting something totally new.BR
BR
BR
Look at my web-site ... 
[[http://elgg.punahou.edu/2010Anthropology/pg/profile/Tiaz51I|http://Www.Ichatroulette.net/]]

[Cassandra Wiki] Trivial Update of Tangela82 by Tangela82

Dear Wiki user,

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

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

New page:
These call the author Leona Rothrock though she doesn't really not unlike being 
called like that. Her tasks is an invoicing officer and she or he will not 
change it in the near future. Alabama has always been her home but this point 
she is considering other possibilities. Her friends say it's not perfect her 
but what she speaks so highly of doing is karaoke but she's struggling to find 
time because of it. If you wish to find out more check to choose from his 
website: http://www.portcontainers.com

[Cassandra Wiki] Trivial Update of PaulinaQu by PaulinaQu

Dear Wiki user,

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

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

New page:
My name: Paulina QuinonesBR
My age: 29BR
Country: AustraliaBR
City: Northfield BR
ZIP: 5085BR
Street: 47 Rupara StreetBR
BR
Here is my weblog - [[http://lotsofriends.com/buy-twitter-followers/|twitter 
followers no password]]

[Cassandra Wiki] Trivial Update of FayeGreen by FayeGreen

Dear Wiki user,

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

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

New page:
Hi, I am Jenna Mahr but My friends and i don't like when people today use my 
full tag. Coing collecting is truly something Which i really enjoy doing. Some 
time inside I opted for to live in Arizona but I will have to action in a good 
year potentially two. I placed to come to be unemployed but now Write-up am 
some transporting and as a consequence receiving police.BR
BR
Here is my website; 
[[http://thisway.altervista.org/groups/the-best-way-to-get-out-of-acne-correct-affordably/|click
 through the up coming web site]]

[Cassandra Wiki] Trivial Update of EfrainBra by EfrainBra

Dear Wiki user,

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

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

New page:
There are many factors that will make one roof completely different from the 
opposite.BR
The Designer along with the occupant have complete control over the Open and 
Breathable Space that may be made. BR
BR
BR
My name: Enid WhatleyBR
My age: 39BR
Country: ItaliaBR
Town: Catania BR
ZIP: 95121BR
Street: Via Varrone 148BR
BR
My weblog; [[http://dachausbauinfo.de/|mouse click the following website page]]

[jira] [Commented] (CASSANDRA-5062) Support CAS

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

Jonathan Ellis commented on CASSANDRA-5062:
---

bq. During prepare, if a replica promise, the ballot it sends back in the
response is the one it just got

This is a bug, it's supposed to reply with the ballot of a previously accepted
value (so the coordinator can pick the highest such to re-propose).

bq. Why not just use a System table for the Paxos state?

I was hoping to avoid that, but you're right.

bq. Should that compare the timestamps of the UUIDs (The clock sequence is not
the timestamp). Furthermore, wasn't the goal to have a comparator to have it
only compare and timestamps (and thus not break tie on same timestamp)?

Yes, and yes.

bq. wasn't the goal to reuse the ballot timestamp as the timestamp of the
columns in the update we finally commit

I'm on board with that, but since we're generating ballots server-side that
means we need to swallow CASSANDRA-5293...

bq. I strongly believe we should return false only if the CAS doesn't apply,
but otherwise we should just restart a new proposal

I agree, but on the other hand just retry automatically is something that we
avoid elsewhere for good reason (arbitrarily high latency with no visibility to
the client what is going on). I also considered introducing a new exception
type explaining the state, but throwing an exception when everything is working
fine is also not intuitive. So I think all the options kind of suck, but this
one sucks least IMO.

Fixes pushed to the same branch.

Support CAS
---

Key: CASSANDRA-5062
URL: https://issues.apache.org/jira/browse/CASSANDRA-5062
Project: Cassandra
Issue Type: New Feature
Components: API, Core
Reporter: Jonathan Ellis
Fix For: 2.0

Attachments: half-baked commit 1.jpg, half-baked commit 2.jpg,
half-baked commit 3.jpg

Strong consistency is not enough to prevent race conditions. The classic
example is user account creation: we want to ensure usernames are unique, so
we only want to signal account creation success if nobody else has created
the account yet. But naive read-then-write allows clients to race and both
think they have a green light to create.

[jira] [Assigned] (CASSANDRA-4775) Counters 2.0


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

Jonathan Ellis reassigned CASSANDRA-4775:
-

Assignee: Aleksey Yeschenko

 Counters 2.0
 

 Key: CASSANDRA-4775
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4775
 Project: Cassandra
  Issue Type: New Feature
  Components: Core
Reporter: Arya Goudarzi
Assignee: Aleksey Yeschenko
  Labels: counters
 Fix For: 2.0


 The existing partitioned counters remain a source of frustration for most 
 users almost two years after being introduced.  The remaining problems are 
 inherent in the design, not something that can be fixed given enough 
 time/eyeballs.
 Ideally a solution would give us
 - similar performance
 - less special cases in the code
 - potential for a retry mechanism

--
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-5338) scripts fail when paths contain space


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

Jonathan Ellis commented on CASSANDRA-5338:
---

So this is redundant post-5301?

 scripts fail when paths contain space
 -

 Key: CASSANDRA-5338
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5338
 Project: Cassandra
  Issue Type: Bug
  Components: Tools
Affects Versions: 1.2.2
 Environment: Kubuntu 12.10 (GNU bash 4.2.37), and Windows XP (msysgit 
 GNU bash 3.1.0)
Reporter: Amichai Rothman
Priority: Minor
 Attachments: fix_spaces_in_paths.patch


 The shell scripts fail when the cassandra or java dirs contain spaces.

--
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-5242) Directories.migrateFile() does not handle -old or -tmp LDB manifests


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

Jonathan Ellis updated CASSANDRA-5242:
--

Reviewer: iamaleksey  (was: amorton)

 Directories.migrateFile() does not handle -old or -tmp LDB manifests 
 -

 Key: CASSANDRA-5242
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5242
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.9, 1.2.0
Reporter: amorton
Assignee: Marcus Eriksson
Priority: Minor
 Fix For: 1.1.11

 Attachments: 0001-CASSANDRA-5242.patch, 0001-CASSANDRA-5242-v2.patch


 During LDB compaction a -old.json file is created with the previous manifest.
 Directories.migrateFile() only checks for the .json extension and uses the 
 length to determine the CF name. 
 This can result in the -old.json manifest getting copied to a CF-old 
 directory in the new layout. 
 see http://www.mail-archive.com/user@cassandra.apache.org/msg27583.html for 
 an example 

--
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-5339) YAML network topology snitch supporting preferred addresses


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

Jonathan Ellis updated CASSANDRA-5339:
--

Reviewer: brandon.williams

 YAML network topology snitch supporting preferred addresses
 ---

 Key: CASSANDRA-5339
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5339
 Project: Cassandra
  Issue Type: New Feature
Reporter: Eric Dong
Priority: Minor
 Attachments: CASSANDRA-5339-1.patch


 In order to support having a Cassandra cluster spanning multiple data 
 centers, some in Amazon EC2 and some not, I'm submitting a YAML network 
 topology snitch that allows one to configure 'preferred addresses' such as a 
 data-center-local address. The new snitch reconnects to the node via the 
 preferred address using the same reconnection trick present in 
 Ec2MultiRegionSnitch.
 I chose a new YAML format instead of trying to extend 
 cassandra-topology.properties because it is easier to read and allows for 
 future extensibility.
 Pull request to follow.

--
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-5341) Select writetime Exception when data doesn't exist


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

Jonathan Ellis updated CASSANDRA-5341:
--

Reviewer: iamaleksey

 Select writetime  Exception when  data doesn't exist
 

 Key: CASSANDRA-5341
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5341
 Project: Cassandra
  Issue Type: Bug
  Components: API
Affects Versions: 1.2.2
Reporter: julien campan
Assignee: Sylvain Lebresne
Priority: Minor
 Fix For: 1.2.4

 Attachments: 5341.txt


 Hi,
 When I try do to a “select writetime” on a empty column, I have an Exception. 
 For example : 
 Create table test (id  int, value int, value2 int, primary key (id)); 
 INSERT INTO test (id, value ) VALUES ( 1,100) ;
 select * from test where id =1; 
 ==
  id | value | value2
 +---+
   1 |   100 |   null  
 It’s working.
 select WRITETIME(value) from test where id =1; 
 ==
  writetime(value)
 --
  1363184789539000
 It’s working
 select WRITETIME(value2) from test where id =1; 
 ==TSocket read 0 bytes
 I have an 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-5374) Errors while opening SSTables on Cassandra start after an outage


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

Arya Goudarzi commented on CASSANDRA-5374:
--

I have got this error too in our cluster on few nodes after upgrading to 1.1.10 
from 1.1.6

 Errors while opening SSTables on Cassandra start after an outage
 

 Key: CASSANDRA-5374
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5374
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.1.9
Reporter: Ivan Sobolev

 Getting plenty of those - is that normal? I thought *tmp files Cassandra 
 generates should guarantee all SSTables will be the ones written in proper 
 state.
 {code}ERROR [SSTableBatchOpen:3] 2013-03-21 19:28:34,030 
 AbstractCassandraDaemon.java (line 135) Exception in thread 
 Thread[SSTableBatchOpen:3,5,main]
 java.io.IOError: java.io.EOFException
 at 
 org.apache.cassandra.io.compress.CompressionMetadata.create(CompressionMetadata.java:63)
 at 
 org.apache.cassandra.io.util.CompressedSegmentedFile$Builder.complete(CompressedSegmentedFile.java:55)
 at 
 org.apache.cassandra.io.sstable.SSTableReader.load(SSTableReader.java:429)
 at 
 org.apache.cassandra.io.sstable.SSTableReader.open(SSTableReader.java:200)
 at 
 org.apache.cassandra.io.sstable.SSTableReader.open(SSTableReader.java:153)
 at 
 org.apache.cassandra.io.sstable.SSTableReader$1.run(SSTableReader.java:242)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 Caused by: java.io.EOFException
 at java.io.DataInputStream.readUnsignedShort(DataInputStream.java:323)
 at java.io.DataInputStream.readUTF(DataInputStream.java:572)
 at java.io.DataInputStream.readUTF(DataInputStream.java:547)
 at 
 org.apache.cassandra.io.compress.CompressionMetadata.init(CompressionMetadata.java:74)
 at 
 org.apache.cassandra.io.compress.CompressionMetadata.create(CompressionMetadata.java:59)
 ... 11 more{code}

--
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-5374) Errors while opening SSTables on Cassandra start after an outage


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

Arya Goudarzi edited comment on CASSANDRA-5374 at 4/1/13 10:56 PM:
---

I have got this error too in our cluster on few nodes after upgrading to 1.1.10 
from 1.1.6. How should I proceed? Restart did not help.

  was (Author: arya):
I have got this error too in our cluster on few nodes after upgrading to 
1.1.10 from 1.1.6
  
 Errors while opening SSTables on Cassandra start after an outage
 

 Key: CASSANDRA-5374
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5374
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.1.9
Reporter: Ivan Sobolev

 Getting plenty of those - is that normal? I thought *tmp files Cassandra 
 generates should guarantee all SSTables will be the ones written in proper 
 state.
 {code}ERROR [SSTableBatchOpen:3] 2013-03-21 19:28:34,030 
 AbstractCassandraDaemon.java (line 135) Exception in thread 
 Thread[SSTableBatchOpen:3,5,main]
 java.io.IOError: java.io.EOFException
 at 
 org.apache.cassandra.io.compress.CompressionMetadata.create(CompressionMetadata.java:63)
 at 
 org.apache.cassandra.io.util.CompressedSegmentedFile$Builder.complete(CompressedSegmentedFile.java:55)
 at 
 org.apache.cassandra.io.sstable.SSTableReader.load(SSTableReader.java:429)
 at 
 org.apache.cassandra.io.sstable.SSTableReader.open(SSTableReader.java:200)
 at 
 org.apache.cassandra.io.sstable.SSTableReader.open(SSTableReader.java:153)
 at 
 org.apache.cassandra.io.sstable.SSTableReader$1.run(SSTableReader.java:242)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 Caused by: java.io.EOFException
 at java.io.DataInputStream.readUnsignedShort(DataInputStream.java:323)
 at java.io.DataInputStream.readUTF(DataInputStream.java:572)
 at java.io.DataInputStream.readUTF(DataInputStream.java:547)
 at 
 org.apache.cassandra.io.compress.CompressionMetadata.init(CompressionMetadata.java:74)
 at 
 org.apache.cassandra.io.compress.CompressionMetadata.create(CompressionMetadata.java:59)
 ... 11 more{code}

--
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-5374) Errors while opening SSTables on Cassandra start after an outage


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

Jonathan Ellis updated CASSANDRA-5374:
--

Assignee: Aleksey Yeschenko

 Errors while opening SSTables on Cassandra start after an outage
 

 Key: CASSANDRA-5374
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5374
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.1.9
Reporter: Ivan Sobolev
Assignee: Aleksey Yeschenko

 Getting plenty of those - is that normal? I thought *tmp files Cassandra 
 generates should guarantee all SSTables will be the ones written in proper 
 state.
 {code}ERROR [SSTableBatchOpen:3] 2013-03-21 19:28:34,030 
 AbstractCassandraDaemon.java (line 135) Exception in thread 
 Thread[SSTableBatchOpen:3,5,main]
 java.io.IOError: java.io.EOFException
 at 
 org.apache.cassandra.io.compress.CompressionMetadata.create(CompressionMetadata.java:63)
 at 
 org.apache.cassandra.io.util.CompressedSegmentedFile$Builder.complete(CompressedSegmentedFile.java:55)
 at 
 org.apache.cassandra.io.sstable.SSTableReader.load(SSTableReader.java:429)
 at 
 org.apache.cassandra.io.sstable.SSTableReader.open(SSTableReader.java:200)
 at 
 org.apache.cassandra.io.sstable.SSTableReader.open(SSTableReader.java:153)
 at 
 org.apache.cassandra.io.sstable.SSTableReader$1.run(SSTableReader.java:242)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 Caused by: java.io.EOFException
 at java.io.DataInputStream.readUnsignedShort(DataInputStream.java:323)
 at java.io.DataInputStream.readUTF(DataInputStream.java:572)
 at java.io.DataInputStream.readUTF(DataInputStream.java:547)
 at 
 org.apache.cassandra.io.compress.CompressionMetadata.init(CompressionMetadata.java:74)
 at 
 org.apache.cassandra.io.compress.CompressionMetadata.create(CompressionMetadata.java:59)
 ... 11 more{code}

--
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-5341) Select writetime Exception when data doesn't exist

2013-04-01 Thread Aleksey Yeschenko (JIRA)


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

Aleksey Yeschenko commented on CASSANDRA-5341:
--

+1

 Select writetime  Exception when  data doesn't exist
 

 Key: CASSANDRA-5341
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5341
 Project: Cassandra
  Issue Type: Bug
  Components: API
Affects Versions: 1.2.2
Reporter: julien campan
Assignee: Sylvain Lebresne
Priority: Minor
 Fix For: 1.2.4

 Attachments: 5341.txt


 Hi,
 When I try do to a “select writetime” on a empty column, I have an Exception. 
 For example : 
 Create table test (id  int, value int, value2 int, primary key (id)); 
 INSERT INTO test (id, value ) VALUES ( 1,100) ;
 select * from test where id =1; 
 ==
  id | value | value2
 +---+
   1 |   100 |   null  
 It’s working.
 select WRITETIME(value) from test where id =1; 
 ==
  writetime(value)
 --
  1363184789539000
 It’s working
 select WRITETIME(value2) from test where id =1; 
 ==TSocket read 0 bytes
 I have an 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 bexozyxkutu088 by bexozyxkutu088

Dear Wiki user,

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

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

New page:
I am a Search engine optimization specialist providing superb resources and 
also tips for many through which wish to create a high income from their 
websites.BR
BR
BR
Here is my weblog :: 
[[http://scrapebrokers.com/four-blackhat-methods-to-build-backlinks|Highly 
recommended Webpage]]

[Cassandra Wiki] Trivial Update of Latesha55 by Latesha55

Dear Wiki user,

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

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

New page:
I am 19 years old and my name is Latesha Franco.BR
BR
I life in Casatisma (Italia).BR
BR
Review my page ... [[http://www.hardwoodcenter.ca/|Lumber liquidators]]

[Cassandra Wiki] Trivial Update of RosarioG2 by RosarioG2

Dear Wiki user,

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

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

New page:
Got nothing to say about myself really.BR
Hurrey Im here and a member of apache.org.BR
BR
BR
I just wish I am useful in some way .BR
BR
Feel free to visit my blog: [[http://Le-g.com|Read the Full Document]]

[jira] [Created] (CASSANDRA-5411) Unexpired hints can potentially create previously deleted rows

Arya Goudarzi created CASSANDRA-5411:


 Summary: Unexpired hints can potentially create previously deleted 
rows
 Key: CASSANDRA-5411
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5411
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.10
 Environment: Ubuntu 10.04
Reporter: Arya Goudarzi


Per discussion here: 
http://www.mail-archive.com/user@cassandra.apache.org/msg28905.html

Hits are TTLed to lowest gc_grace_seconds. If we have hints that are not 
replayed, and the administrator updates schema to have lower gc_grace seconds 
on some CF, chances are compactions will delete tombstones and history of 
delete gets lost. If the deleted row is in some hints CF, since the TTL is not 
updated, chances are it gets replayed and the deleted row comes back to life. 

I think it would be nice as part of schema migration, to also update the TTLs 
on hints that already exists on any nodes hints column family. 

--
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-5411) Unexpired hints can potentially create previously deleted rows

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

Arya Goudarzi updated CASSANDRA-5411:
-

Description:
Per discussion here:
http://www.mail-archive.com/user@cassandra.apache.org/msg28905.html

Hints are TTLed to lowest gc_grace_seconds. If we have hints that are not
replayed, and the administrator updates schema to have lower gc_grace seconds
on some CF, chances are compactions will delete tombstones and history of
delete gets lost. If the deleted row is in some hints CF, since the TTL is not
updated, chances are it gets replayed and the deleted row comes back to life.

I think it would be nice as part of schema migration, to also update the TTLs
on hints that already exists on any nodes hints column family.

was:
Per discussion here:
http://www.mail-archive.com/user@cassandra.apache.org/msg28905.html

Hits are TTLed to lowest gc_grace_seconds. If we have hints that are not
replayed, and the administrator updates schema to have lower gc_grace seconds
on some CF, chances are compactions will delete tombstones and history of
delete gets lost. If the deleted row is in some hints CF, since the TTL is not
updated, chances are it gets replayed and the deleted row comes back to life.

I think it would be nice as part of schema migration, to also update the TTLs
on hints that already exists on any nodes hints column family.

Unexpired hints can potentially create previously deleted rows
--

Key: CASSANDRA-5411
URL: https://issues.apache.org/jira/browse/CASSANDRA-5411
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 1.1.10
Environment: Ubuntu 10.04
Reporter: Arya Goudarzi

Per discussion here:
http://www.mail-archive.com/user@cassandra.apache.org/msg28905.html
Hints are TTLed to lowest gc_grace_seconds. If we have hints that are not
replayed, and the administrator updates schema to have lower gc_grace seconds
on some CF, chances are compactions will delete tombstones and history of
delete gets lost. If the deleted row is in some hints CF, since the TTL is
not updated, chances are it gets replayed and the deleted row comes back to
life.
I think it would be nice as part of schema migration, to also update the TTLs
on hints that already exists on any nodes hints column family.

[jira] [Created] (CASSANDRA-5412) Lots of deleted rows came back to life after upgrade from 1.1.6 to 1.1.10

Arya Goudarzi created CASSANDRA-5412:


 Summary: Lots of deleted rows came back to life after upgrade from 
1.1.6 to 1.1.10
 Key: CASSANDRA-5412
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5412
 Project: Cassandra
  Issue Type: Bug
 Environment: Ubuntu 10.04 LTS
Sun Java 6 u39
1.1.6 and 1.1.10
Reporter: Arya Goudarzi


Also per discussion here:  
http://www.mail-archive.com/user@cassandra.apache.org/msg28905.html

I was not able to find any answers as to why a simple upgrade process could 
bring back a lot of (millions) of deleted rows to life. We have successful 
repairs running on our cluster every night. Unless repair is not doing its job, 
it is not possible to the best of my knowledge that the deleted rows come back 
unless there is a bug. I have previously experienced this issue when I upgraded 
our sandbox cluster. I failed at every single attempt to reproduce the issue by 
restoring a fresh cluster from snapshot, and performing the upgrade from 1.1.6 
to 1.1.10. I even exercised this with the snapshot of our production cluster 
before upgrading and was not successful. So, I finally made the decision to 
upgrade, and guess what?! Millions of deleted rows came back after the upgrade. 

This time I confirmed the timestamps of the deleted rows that came back; they 
were actually before the time there were deleted. So, this is just like when 
tombstones get purged before they get propagated. We use nanosecond precision 
timestamps (19 digits).

My discussion on the mailing list did not lead anywhere, though Aaron helped me 
find one another possible way of this happening by Hinted Handoff which I filed 
a separate ticket for. I don't believe this is an issue for us as we don't have 
nodes down for a long period of time. 


--
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-5411) Unexpired hints can potentially create previously deleted rows


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

Brandon Williams commented on CASSANDRA-5411:
-

I think this is fair, instead of relying solely on the TTL we can check against 
the current gc_grace and skip if necessary.

 Unexpired hints can potentially create previously deleted rows
 --

 Key: CASSANDRA-5411
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5411
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.10
 Environment: Ubuntu 10.04
Reporter: Arya Goudarzi

 Per discussion here: 
 http://www.mail-archive.com/user@cassandra.apache.org/msg28905.html
 Hints are TTLed to lowest gc_grace_seconds. If we have hints that are not 
 replayed, and the administrator updates schema to have lower gc_grace seconds 
 on some CF, chances are compactions will delete tombstones and history of 
 delete gets lost. If the deleted row is in some hints CF, since the TTL is 
 not updated, chances are it gets replayed and the deleted row comes back to 
 life. 
 I think it would be nice as part of schema migration, to also update the TTLs 
 on hints that already exists on any nodes hints column family. 

--
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-5411) Unexpired hints can potentially create previously deleted rows


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

Brandon Williams reassigned CASSANDRA-5411:
---

Assignee: Brandon Williams

 Unexpired hints can potentially create previously deleted rows
 --

 Key: CASSANDRA-5411
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5411
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.10
 Environment: Ubuntu 10.04
Reporter: Arya Goudarzi
Assignee: Brandon Williams

 Per discussion here: 
 http://www.mail-archive.com/user@cassandra.apache.org/msg28905.html
 Hints are TTLed to lowest gc_grace_seconds. If we have hints that are not 
 replayed, and the administrator updates schema to have lower gc_grace seconds 
 on some CF, chances are compactions will delete tombstones and history of 
 delete gets lost. If the deleted row is in some hints CF, since the TTL is 
 not updated, chances are it gets replayed and the deleted row comes back to 
 life. 
 I think it would be nice as part of schema migration, to also update the TTLs 
 on hints that already exists on any nodes hints column family. 

--
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-5411) Unexpired hints can potentially create previously deleted rows


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

Brandon Williams updated CASSANDRA-5411:


Fix Version/s: 1.2.4

 Unexpired hints can potentially create previously deleted rows
 --

 Key: CASSANDRA-5411
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5411
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.10
 Environment: Ubuntu 10.04
Reporter: Arya Goudarzi
Assignee: Brandon Williams
 Fix For: 1.2.4


 Per discussion here: 
 http://www.mail-archive.com/user@cassandra.apache.org/msg28905.html
 Hints are TTLed to lowest gc_grace_seconds. If we have hints that are not 
 replayed, and the administrator updates schema to have lower gc_grace seconds 
 on some CF, chances are compactions will delete tombstones and history of 
 delete gets lost. If the deleted row is in some hints CF, since the TTL is 
 not updated, chances are it gets replayed and the deleted row comes back to 
 life. 
 I think it would be nice as part of schema migration, to also update the TTLs 
 on hints that already exists on any nodes hints column family. 

--
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 ManuelaWC by ManuelaWC

Dear Wiki user,

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

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

New page:
There is nothing to write about me really.BR
BR
My blog; [[HTTP://Howtomakequickmoneyonline85.com/|click through the up coming 
website page]]

[Cassandra Wiki] Trivial Update of ColinCant by ColinCant

Dear Wiki user,

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

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

New page:
I am an online dating expert and dating coach who helps men and women get more 
dates online!BR
BR
I am pleased to be a part of apache.orgBR
BR
My website: 
[[http://www.online-dating-automator.com/online-dating-automator-support-options/documentation/|Read
 Even more]]

[Cassandra Wiki] Trivial Update of SMMAllen by SMMAllen