Re: Read after Write inconsistent at times

[Ben Slater]

Have you checked that NTP is correctly synched across all nodes in your
cluster?

On Fri, 24 Feb 2017 at 17:29 Charulata Sharma (charshar) 
wrote:

>
> Hi All,
>
> In my application sometimes I cannot read data that just got inserted.
> This happens very intermittently. Both write and read use LOCAL QUOROM.
>
> We have a cluster of 12 nodes which spans across 2 Data Centers and a RF
> of 3.
>
> Has anyone encountered this problem and if yes what steps have you taken
> to solve it
>
> Thanks,
> Charu
>
-- 


*Ben Slater*

*Chief Product Officer *

   


Read our latest technical blog posts here
.

This email has been sent on behalf of Instaclustr Pty. Limited (Australia)
and Instaclustr Inc (USA).

This email and any attachments may contain confidential and legally
privileged information.  If you are not the intended recipient, do not copy
or disclose its content, but please reply to this email immediately and
highlight the error to the sender and then immediately delete the message.

Read after Write inconsistent at times

[Charulata Sharma (charshar)]

Hi All,

In my application sometimes I cannot read data that just got inserted. This 
happens very intermittently. Both write and read use LOCAL QUOROM.

We have a cluster of 12 nodes which spans across 2 Data Centers and a RF of 3.

Has anyone encountered this problem and if yes what steps have you taken to 
solve it

Thanks,
Charu

Re: [RELEASE] Apache Cassandra 3.0.11 released

[Michael Shuler]

This is correct, we use reprepro and leave the old versions in the pool.

I'm not exactly sure what you mean by "put them back to the apt cache",
Julien. The only thing needed for a downgrade is:
  `wget $URL && dpkg -i cassandra*.deb`

If you run lots of servers on a specific version, then I'd suggest
dropping the specific version you need in a local apt repo and use
`dpkg-scanpackages`.

Basically, it's intentional for a) getting users installing the latest
version, b) saving on download size of metadata, and probably most
importantly c) not needing a release manager to maintain a complete
local debian archive in order to scan every old version for every
release forever. We just build and upload the latest with reprepro.

-- 
Kind regards,
Michael

On 02/23/2017 07:28 PM, Murukesh Mohanan wrote:
> This is speculation on my part, but this might be due to the software used
> to set up the repository. reprepro is very simple to use (and so, somewhat
> popular), but it only supports one version of a package at a time. Older
> deb files are not removed, but they do get dropped from the Packages file.
> This repo might be setup using reprepro.
> 
> On Fri, 24 Feb 2017 at 08:29 Julien Anguenot  wrote:
> 
>> Hey,
>>
>> Any reasons why old versions get removed from the Debian repository when a
>> new version gets promoted?
>>
>> For instance, here one would expect to still be able to:
>>
>>   $ apt-get install cassandra=3.0.10
>>
>> But after that release only the latest 3.0.11 is available:
>>
>>
>> http://dl.bintray.com/apache/cassandra/dists/30x/main/binary-amd64/Packages
>>
>> Old versions are still available from there:
>>
>>http://dl.bintray.com/apache/cassandra/pool/main/c/cassandra/ <
>> http://dl.bintray.com/apache/cassandra/pool/main/c/cassandra/>
>>
>> But it requires to manually download and put them back to the apt cache.
>>
>> It is quite handy for point releases when a rollback is required, and
>> possible, because of regressions.
>>
>> Thanks.
>>
>>J.
>>
>> --
>> Julien Anguenot (@anguenot)
>>
>>> On Feb 21, 2017, at 12:03 PM, Michael Shuler 
>> wrote:
>>>
>>> The Cassandra team is pleased to announce the release of Apache
>>> Cassandra version 3.0.11.
>>>
>>> Apache Cassandra is a fully distributed database. It is the right choice
>>> when you need scalability and high availability without compromising
>>> performance.
>>>
>>> http://cassandra.apache.org/
>>>
>>> Downloads of source and binary distributions are listed in our download
>>> section:
>>>
>>> http://cassandra.apache.org/download/
>>>
>>> This version is a bug fix release[1] on the 3.0 series. As always,
>>> please pay attention to the release notes[2] and Let us know[3] if you
>>> were to encounter any problem.
>>>
>>> Enjoy!
>>>
>>> [1]: (CHANGES.txt)
>>>
>> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.0.11
>>> [2]: (NEWS.txt)
>>>
>> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.0.11
>>> [3]: https://issues.apache.org/jira/browse/CASSANDRA
>>>
>>
>> --
> 
> Murukesh Mohanan,
> Yahoo! Japan
> 

Re: [RELEASE] Apache Cassandra 3.0.11 released

[Julien Anguenot]

Hey, 

Any reasons why old versions get removed from the Debian repository when a new 
version gets promoted?

For instance, here one would expect to still be able to:

  $ apt-get install cassandra=3.0.10

But after that release only the latest 3.0.11 is available:

   http://dl.bintray.com/apache/cassandra/dists/30x/main/binary-amd64/Packages

Old versions are still available from there:

   http://dl.bintray.com/apache/cassandra/pool/main/c/cassandra/ 


But it requires to manually download and put them back to the apt cache.

It is quite handy for point releases when a rollback is required, and possible, 
because of regressions.

Thanks. 

   J.

--
Julien Anguenot (@anguenot)

> On Feb 21, 2017, at 12:03 PM, Michael Shuler  wrote:
> 
> The Cassandra team is pleased to announce the release of Apache
> Cassandra version 3.0.11.
> 
> Apache Cassandra is a fully distributed database. It is the right choice
> when you need scalability and high availability without compromising
> performance.
> 
> http://cassandra.apache.org/
> 
> Downloads of source and binary distributions are listed in our download
> section:
> 
> http://cassandra.apache.org/download/
> 
> This version is a bug fix release[1] on the 3.0 series. As always,
> please pay attention to the release notes[2] and Let us know[3] if you
> were to encounter any problem.
> 
> Enjoy!
> 
> [1]: (CHANGES.txt)
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.0.11
> [2]: (NEWS.txt)
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.0.11
> [3]: https://issues.apache.org/jira/browse/CASSANDRA
> 

Re: Cassandra version numbering

[Jim Witschey]

> Is ver 3.0.10 same as 3.10.

They are different. In particular:

- 3.0.10 contains the features in versions 3.0.0, but with bugfixes.
It's the next in the series of 3.0.0, 3.0.1, 3.0.2, and so on to 3.0.9
and 3.0.10. Typically, 3.0.X releases don't add major features,
instead being smaller bugfix releases.
- 3.10 contains major changes added since 3.9. It's the next in the
series of 3.0, 3.1, 3.2, and so on to 3.9 and 3.10. Any of those
releases may have added major features.

For a more thorough discussion of software version numbers in general,
see this Wikipedia page:

https://en.wikipedia.org/wiki/Software_versioning#Change_significance

For a discussion about the intent of version numbering in Apache
Cassandra 3.0.X and 3.X, see this post from former project chair
Jonathan Ellis:

http://www.mail-archive.com/user@cassandra.apache.org/msg42737.html

Jim

Re: Cassandra version numbering

[Jon Haddad]

No

> On Feb 23, 2017, at 1:59 PM, Rakesh Kumar  wrote:
> 
> Is ver 3.0.10 same as 3.10.
> 
> Cassandra website mentions this: Cassandra 3.10 Changelog
> 
> But in other places 3.0.10 is mentioned.

Cassandra version numbering

[Rakesh Kumar]

Is ver 3.0.10 same as 3.10.

Cassandra website mentions this: Cassandra 3.10 Changelog

But in other places 3.0.10 is mentioned.

Read exceptions after upgrading to 3.0.10

[Meg Mara]

Hello,

We have a 6 node cluster which was recently upgraded from 2.2.5 to 3.0.10. 
Since then, we have been facing a lot of these exceptions. What could be the 
possible cause for this exception?

INFO  [SharedPool-Worker-2] 2017-02-23 20:14:04,984 Message.java:611 - 
Unexpected exception during request; channel = [id: 0x034e0914, 
/xx.xx.117.34:19836 :> /xx.xx.9.119:9042]
java.io.IOException: Error while read(...): Connection reset by peer
  at io.netty.channel.epoll.Native.readAddress(Native Method) 
~[netty-all-4.0.23.Final.jar:4.0.23.Final]
  at 
io.netty.channel.epoll.EpollSocketChannel$EpollSocketUnsafe.doReadBytes(EpollSocketChannel.java:675)
 ~[netty-all-4.0.23.Final.jar:4.0.23.Final]
  at 
io.netty.channel.epoll.EpollSocketChannel$EpollSocketUnsafe.epollInReady(EpollSocketChannel.java:714)
 ~[netty-all-4.0.23.Final.jar:4.0.23.Final]
  at 
io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:326) 
~[netty-all-4.0.23.Final.jar:4.0.23.Final]
  at 
io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:264) 
~[netty-all-4.0.23.Final.jar:4.0.23.Final]
  at 
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116)
 ~[netty-all-4.0.23.Final.jar:4.0.23.Final]
  at 
io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)
 ~[netty-all-4.0.23.Final.jar:4.0.23.Final]
  at java.lang.Thread.run(Thread.java:745) [na:1.8.0_101]

INFO  [ScheduledTasks:1] 2017-02-23 20:13:12,330 StatusLogger.java:52 - Pool 
NameActive   Pending  Completed   Blocked  All Time 
Blocked
INFO  [ScheduledTasks:1] 2017-02-23 20:13:12,340 StatusLogger.java:56 - 
MutationStage 0 0  88103 0  
   0
INFO  [ScheduledTasks:1] 2017-02-23 20:13:12,340 StatusLogger.java:56 - 
ViewMutationStage 0 0  0 0  
   0
INFO  [ScheduledTasks:1] 2017-02-23 20:13:12,340 StatusLogger.java:56 - 
ReadStage 0 0 155903 0  
   0
INFO  [ScheduledTasks:1] 2017-02-23 20:13:12,340 StatusLogger.java:56 - 
RequestResponseStage  0 0 188450 0  
   0
INFO  [ScheduledTasks:1] 2017-02-23 20:13:12,341 StatusLogger.java:56 - 
ReadRepairStage   0 0   4118 0  
   0
INFO  [ScheduledTasks:1] 2017-02-23 20:13:12,341 StatusLogger.java:56 - 
CounterMutationStage  0 0  0 0  
   0
INFO  [ScheduledTasks:1] 2017-02-23 20:13:12,341 StatusLogger.java:56 - 
MiscStage 0 0  0 0  
   0
INFO  [ScheduledTasks:1] 2017-02-23 20:13:12,341 StatusLogger.java:56 - 
CompactionExecutor0 0  20443 0  
   0
INFO  [ScheduledTasks:1] 2017-02-23 20:13:12,342 StatusLogger.java:56 - 
MemtableReclaimMemory 0 0 52 0  
   0
INFO  [ScheduledTasks:1] 2017-02-23 20:13:12,342 StatusLogger.java:56 - 
PendingRangeCalculator0 0  8 0  
   0
INFO  [ScheduledTasks:1] 2017-02-23 20:13:12,342 StatusLogger.java:56 - 
GossipStage   0 0  21308 0  
   0
INFO  [ScheduledTasks:1] 2017-02-23 20:13:12,345 StatusLogger.java:56 - 
Native-Transport-Requests 0 0 155489 0  
   4

INFO  [ScheduledTasks:1] 2017-02-23 20:13:12,346 StatusLogger.java:103 - Table  
 Memtable ops,data
INFO  [ScheduledTasks:1] 2017-02-23 20:13:12,346 StatusLogger.java:106 - look   
300,21900
INFO  [ScheduledTasks:1] 2017-02-23 20:13:12,346 StatusLogger.java:106 - 
segment   8,336
INFO  [ScheduledTasks:1] 2017-02-23 20:13:12,347 StatusLogger.java:106 - 
sys_spend 13,5678
INFO  [ScheduledTasks:1] 2017-02-23 20:13:12,347 StatusLogger.java:106 - list   
  0,0
INFO  [ScheduledTasks:1] 2017-02-23 20:13:12,347 StatusLogger.java:106 - 
a_count   14,392
INFO  [ScheduledTasks:1] 2017-02-23 20:13:12,347 StatusLogger.java:106 - 
r_count   618,79787
INFO  [ScheduledTasks:1] 2017-02-23 20:13:12,347 StatusLogger.java:106 - 
sys_prd 642,1393965

Thank you in advance,
Meghana Mara