Hi Oskar,
I know this won't help you as quickly as you would like but please consider
updating the JIRA issue with details of your environment as it may help
move the investigation along.
Good luck!
On Tue, Jun 21, 2016 at 12:21 PM, Julien Anguenot
wrote:
> You could try to sstabledump that on
You could try to sstabledump that one corrupted table, write some
(Python) code to get rid of the duplicates processing that stabledump
output (might not be bullet proof depending on data, I agree),
truncate and re-insert them back in that table without duplicates.
On Tue, Jun 21, 2016 at 11:52 AM
AFAICT, the issue does not seem to be driver related as the duplicates
where showing up both using the cqlsh and Java driver. In addition,
the sstabledump output contained the actual duplicates. (see Jira
issue)
On Tue, Jun 21, 2016 at 12:04 PM, Oskar Kjellin wrote:
> Did you see similar issues w
Did you see similar issues when querying using a driver? Because we get no
results in the driver what so ever
Sent from my iPhone
> On 21 juni 2016, at 18:50, Julien Anguenot wrote:
>
> See my comments on the issue: I had to truncate and reinsert data in
> these corrupted tables.
>
> AFAIK,
Hmm, no way we can do that in prod :/
Sent from my iPhone
> On 21 juni 2016, at 18:50, Julien Anguenot wrote:
>
> See my comments on the issue: I had to truncate and reinsert data in
> these corrupted tables.
>
> AFAIK, there is no evidence that UDTs are responsible of this bad behavior.
>
>>
See my comments on the issue: I had to truncate and reinsert data in
these corrupted tables.
AFAIK, there is no evidence that UDTs are responsible of this bad behavior.
On Tue, Jun 21, 2016 at 11:45 AM, Oskar Kjellin wrote:
> Yea I saw that one. We're not using UDT in the affected tables tho.
>
Yea I saw that one. We're not using UDT in the affected tables tho.
Did you resolve it?
Sent from my iPhone
> On 21 juni 2016, at 18:27, Julien Anguenot wrote:
>
> I have experienced similar duplicate primary keys behavior with couple
> of tables after upgrading from 2.2.x to 3.0.x.
>
> See
I have experienced similar duplicate primary keys behavior with couple
of tables after upgrading from 2.2.x to 3.0.x.
See comments on the Jira issue I opened at the time over there:
https://issues.apache.org/jira/browse/CASSANDRA-11887
On Tue, Jun 21, 2016 at 10:47 AM, Oskar Kjellin wrote:
> Hi
