date:20161102

Re: Bug in paging reads and limit reads (short reads!)

2016-11-02 Thread Benjamin Lerer

Hi Bhaskar,

Thanks for reporting that problem. It is a nice catch :-)

Could you open a JIRA ticket with all the information that you provided?

I will try to fix that problem.

Benjamin


On Wed, Nov 2, 2016 at 12:00 AM, Bhaskar Muppana 
wrote:

> Hi Guys,
>
> We are seeing an issue with paging reads missing some small number of
> columns when we do paging/limit reads. We get this on a single DC cluster
> itself when both reads and writes are happening with QUORUM. Paging/limit
> reads see this issue. I have attached the ccm based script which reproduces
> the problem.
>
> * Keyspace RF - 2
> * Table (id int, course text, marks int, primary key(id, course))
> * replicas for partition key 1 - r1, r2 and r3
> * insert (1, '1', 1) ,  (1, '2', 2),  (1, '3', 3),  (1, '4', 4),  (1, '5',
> 5) - succeeded on all 3 replicas
> * insert (1, '6', 6) succeeded on r1 and r3, failed on r2
> * delete (1, '2'), (1, '3'), (1, '4'), (1, '5') succeeded on r1 and r2,
> failed on r3
> * insert (1, '7', 7) succeeded on r1 and r2, failed on r3
>
> Local data on 3 nodes looks like as below now
>
> r1: (1, '1', 1), tombstone(2-5 records), (1, '6', 6), (1, '7', 7)
> r2: (1, '1', 1), tombstone(2-5 records), (1, '7', 7)
> r3: (1, '1', 1),  (1, '2', 2),  (1, '3', 3),  (1, '4', 4),  (1, '5',
> 5), (1, '6', 6)
>
> If we do a paging read with page_size 2, and if it gets data from r2 and
> r3, then it will only get the data (1, '1', 1) and (1, '7', 7) skipping
> record 6. This problem would happen if the same query is not doing paging
> but limit set to 2 records.
>
> Resolution code for reads works same for paging queries and normal
> queries. Co-ordinator shouldn't respond back to client with records/columns
> that it didn't have complete visibility on all required replicas (in this
> case 2 replicas). In above case, it is sending back record (1, '7', 7) back
> to client, but its visibility on r3 is limited up to (1, '2', 2) and it is
> relying on just r2 data to assume (1, '6', 6) doesn't exist, which is
> wrong. End of the resolution all it can conclusively say any thing about is
> (1, '1', 1), which exists and (1, '2', 2), which is deleted.
>
> Ideally we should have different resolution implementation for
> paging/limit queries.
>
> We could reproduce this on 2.0.17, 2.1.16 and 3.0.9.
>
> Seems like 3.0.9 we have ShortReadProtection transformation on list
> queries. I assume that is to protect against the cases like above. But, we
> can reproduce the issue in 3.0.9 as well.
>
> Thanks,
> Bhaskar
>
>
>
>
>
>
>

[GitHub] cassandra pull request #80: CASSANDRA-12869: Don't load mx4j beans twice

2016-11-02 Thread nastra

GitHub user nastra opened a pull request:

https://github.com/apache/cassandra/pull/80

CASSANDRA-12869: Don't load mx4j beans twice



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/nastra/cassandra 12869-3.X

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/80.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #80


commit cb989c427e401eb2375aa9226551573ac3ff9a37
Author: Eduard Tudenhoefner 
Date:   2016-11-02T08:31:30Z

CASSANDRA-12869: Don't load mx4j beans twice




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request #81: 12869 trunk

2016-11-02 Thread nastra

GitHub user nastra opened a pull request:

https://github.com/apache/cassandra/pull/81

12869 trunk



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/nastra/cassandra 12869-trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cassandra/pull/81.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #81


commit cb989c427e401eb2375aa9226551573ac3ff9a37
Author: Eduard Tudenhoefner 
Date:   2016-11-02T08:31:30Z

CASSANDRA-12869: Don't load mx4j beans twice

commit 12145583dc355f97524c5e271bb918be62652401
Author: Eduard Tudenhoefner 
Date:   2016-11-02T08:36:51Z

Merge branch '12869-3.X' into 12869-trunk




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Many failing unit tests, prior to any changes. NoSuchFieldError: rpc_port

2016-11-02 Thread BORIS MELAMED

Thank you Nate, I followed those instructions as well, and I can run/debug
Cassandra without issues. It's only when I run the test suite that I get
those errors.

(By the way, I meant to write OS-X, not iOS, of course)

-Boris

On Tue, Nov 1, 2016 at 8:24 PM, Nate McCall  wrote:

> Hi Boris,
> Did you see this section on the site:
> http://cassandra.apache.org/doc/latest/development/ide.
> html#setting-up-cassandra-in-intellij-idea
>
> I've not had a problem setting everything up in IntelliJ following
> that process.
>
> On Wed, Nov 2, 2016 at 3:04 AM, BORIS MELAMED 
> wrote:
> > Hello,
> >
> > (If there is a more appropriate channel for posing my question, please
> > point me to it.)
> >
> > I have created my own fork of the Cassandra trunk, and prior to making
> any
> > changes, have built and run 'build - test' in my IDEA env, iOS.
> > I'm getting:
> >
> > Ant build completed with 296 errors and 792 warnings in 11m 57s at
> > 10/31/16, 1:22 PM
> >
> > Running tests from command line seems to give the same results (I did not
> > wait, but many similar errors).
> >
> > Many errors like this:
> >
> > Testcase: org.apache.cassandra.triggers.TriggersSchemaTest: Caused an
> ERROR
> > rpc_port
> > java.lang.NoSuchFieldError: rpc_port
> > at
> > org.apache.cassandra.OffsetAwareConfigurationLoader.loadConfig(
> OffsetAwareConfigurationLoader.java:52)
> > at
> > org.apache.cassandra.config.DatabaseDescriptor.loadConfig(
> DatabaseDescriptor.java:261)
> > at
> > org.apache.cassandra.config.DatabaseDescriptor.daemonInitialization(
> DatabaseDescriptor.java:140)
> > at org.apache.cassandra.cql3.CQLTester.(CQLTester.java:101)
> > at org.apache.cassandra.SchemaLoader.prepareServer(SchemaLoader.java:69)
> > at org.apache.cassandra.SchemaLoader.loadSchema(SchemaLoader.java:51)
> > at
> > org.apache.cassandra.triggers.TriggersSchemaTest.beforeTest(
> TriggersSchemaTest.java:45)
> >
> >
> > Test org.apache.cassandra.triggers.TriggersSchemaTest FAILED
> >
> >
> > But code shows the Config class to have this field defined:
> >
> > public int rpc_port = 9160;
> >
> > Any advice?
> >
> > ---
> > *Boris Melamed*  |Software Engineer
> > *w:* ++972-545691126  *e: boris.mela...@weather.com
> > *
> >  
> >  
> >  
>

Re: [VOTE] Release Apache Cassandra 3.0.10

2016-11-02 Thread Sylvain Lebresne

+1

On Mon, Oct 31, 2016 at 6:29 PM, Nate McCall  wrote:

> +1
>
> On Tue, Nov 1, 2016 at 3:12 AM, Michael Shuler 
> wrote:
> > I propose the following artifacts for release as 3.0.10.
> >
> > sha1: 817ba038783212b716f6981b26c8348ffdc92f59
> > Git:
> > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=
> shortlog;h=refs/tags/3.0.10-tentative
> > Artifacts:
> > https://repository.apache.org/content/repositories/
> orgapachecassandra-1131/org/apache/cassandra/apache-cassandra/3.0.10/
> > Staging repository:
> > https://repository.apache.org/content/repositories/
> orgapachecassandra-1131/
> >
> > The Debian packages are available here: http://people.apache.org/~
> mshuler
> >
> > The vote will be open for 72 hours (longer if needed).
> >
> > [1]: (CHANGES.txt) https://goo.gl/4e1P3e
> > [2]: (NEWS.txt) https://goo.gl/AwLFr1
>

Re: Many failing unit tests, prior to any changes. NoSuchFieldError: rpc_port

2016-11-02 Thread Licata, Christopher (CONT)

I have actually noticed the same thing when I was working on 
https://issues.apache.org/jira/browse/CASSANDRA-12485.  Even before I made any 
changes to cassandra-trunk.  I was seeing failing unit tests.  Not sure if the 
TriggersSchemaTest was the exact test though. 

Thanks,
Christopher Licata
Senior Software Engineer
Capital One-Card Rewards
718.916.8940

On 11/2/16, 5:02 AM, "BORIS MELAMED"  wrote:

Thank you Nate, I followed those instructions as well, and I can run/debug
Cassandra without issues. It's only when I run the test suite that I get
those errors.

(By the way, I meant to write OS-X, not iOS, of course)

-Boris

On Tue, Nov 1, 2016 at 8:24 PM, Nate McCall  wrote:

> Hi Boris,
> Did you see this section on the site:
> http://cassandra.apache.org/doc/latest/development/ide.
> html#setting-up-cassandra-in-intellij-idea
>
> I've not had a problem setting everything up in IntelliJ following
> that process.
>
> On Wed, Nov 2, 2016 at 3:04 AM, BORIS MELAMED 
> wrote:
> > Hello,
> >
> > (If there is a more appropriate channel for posing my question, please
> > point me to it.)
> >
> > I have created my own fork of the Cassandra trunk, and prior to making
> any
> > changes, have built and run 'build - test' in my IDEA env, iOS.
> > I'm getting:
> >
> > Ant build completed with 296 errors and 792 warnings in 11m 57s at
> > 10/31/16, 1:22 PM
> >
> > Running tests from command line seems to give the same results (I did 
not
> > wait, but many similar errors).
> >
> > Many errors like this:
> >
> > Testcase: org.apache.cassandra.triggers.TriggersSchemaTest: Caused an
> ERROR
> > rpc_port
> > java.lang.NoSuchFieldError: rpc_port
> > at
> > org.apache.cassandra.OffsetAwareConfigurationLoader.loadConfig(
> OffsetAwareConfigurationLoader.java:52)
> > at
> > org.apache.cassandra.config.DatabaseDescriptor.loadConfig(
> DatabaseDescriptor.java:261)
> > at
> > org.apache.cassandra.config.DatabaseDescriptor.daemonInitialization(
> DatabaseDescriptor.java:140)
> > at org.apache.cassandra.cql3.CQLTester.(CQLTester.java:101)
> > at org.apache.cassandra.SchemaLoader.prepareServer(SchemaLoader.java:69)
> > at org.apache.cassandra.SchemaLoader.loadSchema(SchemaLoader.java:51)
> > at
> > org.apache.cassandra.triggers.TriggersSchemaTest.beforeTest(
> TriggersSchemaTest.java:45)
> >
> >
> > Test org.apache.cassandra.triggers.TriggersSchemaTest FAILED
> >
> >
> > But code shows the Config class to have this field defined:
> >
> > public int rpc_port = 9160;
> >
> > Any advice?
> >
> > ---
> > *Boris Melamed*  |Software Engineer
> > *w:* ++972-545691126  *e: boris.mela...@weather.com
> > *
> >  
> >  
> >  
>

The information contained in this e-mail is confidential and/or proprietary to 
Capital One and/or its affiliates and may only be used solely in performance of 
work or services for Capital One. The information transmitted herewith is 
intended only for use by the individual or entity to which it is addressed. If 
the reader of this message is not the intended recipient, you are hereby 
notified that any review, retransmission, dissemination, distribution, copying 
or other use of, or taking of any action in reliance upon this information is 
strictly prohibited. If you have received this communication in error, please 
contact the sender and delete the material from your computer.

Re: Many failing unit tests, prior to any changes. NoSuchFieldError: rpc_port

2016-11-02 Thread BORIS MELAMED

Actually, 279 out of 296 failing tests seem to fail with this same error:
java.lang.NoSuchFieldError: rpc_port
at org.apache.cassandra.OffsetAwareConfigurationLoader.loadConfig(
OffsetAwareConfigurationLoader.java:52)


*Boris Melamed*  |Software Engineer
*w:* ++972-545691126  *e: boris.mela...@weather.com
*
 
 
 

On Wed, Nov 2, 2016 at 3:22 PM, Licata, Christopher (CONT) <
christopher.lic...@capitalone.com> wrote:

> I have actually noticed the same thing when I was working on
> https://issues.apache.org/jira/browse/CASSANDRA-12485.  Even before I
> made any changes to cassandra-trunk.  I was seeing failing unit tests.  Not
> sure if the TriggersSchemaTest was the exact test though.
>
>
> Thanks,
> Christopher Licata
> Senior Software Engineer
> Capital One-Card Rewards
> 718.916.8940
>
>
>
> On 11/2/16, 5:02 AM, "BORIS MELAMED"  wrote:
>
> Thank you Nate, I followed those instructions as well, and I can
> run/debug
> Cassandra without issues. It's only when I run the test suite that I
> get
> those errors.
>
> (By the way, I meant to write OS-X, not iOS, of course)
>
> -Boris
>
> On Tue, Nov 1, 2016 at 8:24 PM, Nate McCall 
> wrote:
>
> > Hi Boris,
> > Did you see this section on the site:
> > http://cassandra.apache.org/doc/latest/development/ide.
> > html#setting-up-cassandra-in-intellij-idea
> >
> > I've not had a problem setting everything up in IntelliJ following
> > that process.
> >
> > On Wed, Nov 2, 2016 at 3:04 AM, BORIS MELAMED <
> boris.mela...@weather.com>
> > wrote:
> > > Hello,
> > >
> > > (If there is a more appropriate channel for posing my question,
> please
> > > point me to it.)
> > >
> > > I have created my own fork of the Cassandra trunk, and prior to
> making
> > any
> > > changes, have built and run 'build - test' in my IDEA env, iOS.
> > > I'm getting:
> > >
> > > Ant build completed with 296 errors and 792 warnings in 11m 57s at
> > > 10/31/16, 1:22 PM
> > >
> > > Running tests from command line seems to give the same results (I
> did not
> > > wait, but many similar errors).
> > >
> > > Many errors like this:
> > >
> > > Testcase: org.apache.cassandra.triggers.TriggersSchemaTest:
> Caused an
> > ERROR
> > > rpc_port
> > > java.lang.NoSuchFieldError: rpc_port
> > > at
> > > org.apache.cassandra.OffsetAwareConfigurationLoader.loadConfig(
> > OffsetAwareConfigurationLoader.java:52)
> > > at
> > > org.apache.cassandra.config.DatabaseDescriptor.loadConfig(
> > DatabaseDescriptor.java:261)
> > > at
> > > org.apache.cassandra.config.DatabaseDescriptor.
> daemonInitialization(
> > DatabaseDescriptor.java:140)
> > > at org.apache.cassandra.cql3.CQLTester.(CQLTester.
> java:101)
> > > at org.apache.cassandra.SchemaLoader.prepareServer(
> SchemaLoader.java:69)
> > > at org.apache.cassandra.SchemaLoader.loadSchema(
> SchemaLoader.java:51)
> > > at
> > > org.apache.cassandra.triggers.TriggersSchemaTest.beforeTest(
> > TriggersSchemaTest.java:45)
> > >
> > >
> > > Test org.apache.cassandra.triggers.TriggersSchemaTest FAILED
> > >
> > >
> > > But code shows the Config class to have this field defined:
> > >
> > > public int rpc_port = 9160;
> > >
> > > Any advice?
> > >
> > > ---
> > > *Boris Melamed*  |Software Engineer
> > > *w:* ++972-545691126  *e: boris.mela...@weather.com
> > > *
> > >  
> > >  
> > >  
> >
>
>
>
> 
>
> The information contained in this e-mail is confidential and/or
> proprietary to Capital One and/or its affiliates and may only be used
> solely in performance of work or services for Capital One. The information
> transmitted herewith is intended only for use by the individual or entity
> to which it is addressed. If the reader of this message is not the intended
> recipient, you are hereby notified that any review, retransmission,
> dissemination, distribution, copying or other use of, or taking of any
> action in reliance upon this information is strictly prohibited. If you
> have received this communication in error, please contact the sender and
> delete the material from your computer.
>

Re: Many failing unit tests, prior to any changes. NoSuchFieldError: rpc_port

2016-11-02 Thread Licata, Christopher (CONT)

Yea, sorry.  I never got that many failing tests.  Perhaps it could be 
environment variable related.   

Thanks,
Christopher Licata
Senior Software Engineer
Featureless Tech Monsters
Card Rewards
718.916.8940



On 11/2/16, 10:10 AM, "BORIS MELAMED"  wrote:

Actually, 279 out of 296 failing tests seem to fail with this same error:
java.lang.NoSuchFieldError: rpc_port
at org.apache.cassandra.OffsetAwareConfigurationLoader.loadConfig(
OffsetAwareConfigurationLoader.java:52)






The information contained in this e-mail is confidential and/or proprietary to 
Capital One and/or its affiliates and may only be used solely in performance of 
work or services for Capital One. The information transmitted herewith is 
intended only for use by the individual or entity to which it is addressed. If 
the reader of this message is not the intended recipient, you are hereby 
notified that any review, retransmission, dissemination, distribution, copying 
or other use of, or taking of any action in reliance upon this information is 
strictly prohibited. If you have received this communication in error, please 
contact the sender and delete the material from your computer.

Re: [VOTE] Release Apache Cassandra 3.10

2016-11-02 Thread Nate McCall

Sorry all. Changing my vote to -1 per my comment:
https://issues.apache.org/jira/browse/CASSANDRA-12867?focusedCommentId=15630442&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15630442

This pattern is more common in the wild than you might think.

On Tue, Nov 1, 2016 at 11:14 AM, kurt Greaves  wrote:
> Just raised https://issues.apache.org/jira/browse/CASSANDRA-12867 which
> affects 3.10 and 3.0.10. Appears to be a bug introduced by CASSANDRA-12060.
> Might want to consider it before releasing these versions.
>
> Kurt Greaves
> k...@instaclustr.com
> www.instaclustr.com
>
> On 31 October 2016 at 17:41, Brandon Williams  wrote:
>
>> +1
>>
>> On Mon, Oct 31, 2016 at 10:18 AM, Michael Shuler 
>> wrote:
>>
>> > I propose the following artifacts for release as 3.10.
>> >
>> > sha1: a3828ca8b755fc98799867baf07039f7ff53be05
>> > Git:
>> > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=
>> > shortlog;h=refs/tags/3.10-tentative
>> > Artifacts:
>> > https://repository.apache.org/content/repositories/
>> > orgapachecassandra-1130/org/apache/cassandra/apache-cassandra/3.10/
>> > Staging repository:
>> > https://repository.apache.org/content/repositories/
>> > orgapachecassandra-1130/
>> >
>> > The Debian packages are available here: http://people.apache.org/~
>> mshuler
>> >
>> > The vote will be open for 72 hours (longer if needed).
>> >
>> > [1]: (CHANGES.txt) https://goo.gl/8uMiBt
>> > [2]: (NEWS.txt) https://goo.gl/prKdlZ
>> >
>>

Re: [VOTE] Release Apache Cassandra 3.0.10

2016-11-02 Thread Nate McCall

[Copied from 3.10 thread]
Sorry all. Changing my vote to -1 per my comment:
https://issues.apache.org/jira/browse/CASSANDRA-12867?focusedCommentId=15630442&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15630442

This pattern is more common in the wild than you might think.

On Thu, Nov 3, 2016 at 2:03 AM, Sylvain Lebresne  wrote:
> +1
>
> On Mon, Oct 31, 2016 at 6:29 PM, Nate McCall  wrote:
>
>> +1
>>
>> On Tue, Nov 1, 2016 at 3:12 AM, Michael Shuler 
>> wrote:
>> > I propose the following artifacts for release as 3.0.10.
>> >
>> > sha1: 817ba038783212b716f6981b26c8348ffdc92f59
>> > Git:
>> > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=
>> shortlog;h=refs/tags/3.0.10-tentative
>> > Artifacts:
>> > https://repository.apache.org/content/repositories/
>> orgapachecassandra-1131/org/apache/cassandra/apache-cassandra/3.0.10/
>> > Staging repository:
>> > https://repository.apache.org/content/repositories/
>> orgapachecassandra-1131/
>> >
>> > The Debian packages are available here: http://people.apache.org/~
>> mshuler
>> >
>> > The vote will be open for 72 hours (longer if needed).
>> >
>> > [1]: (CHANGES.txt) https://goo.gl/4e1P3e
>> > [2]: (NEWS.txt) https://goo.gl/AwLFr1
>>

Re: Bug in paging reads and limit reads (short reads!)

2016-11-02 Thread Bhaskar Muppana

Thanks Benjamin! I am also hoping to ask couple of questions on difference
in this code base between 2.0, 2.1 and 3.0. I understand 2.0 is closed from
community point of view. But, we are still using in some cases, so we need
to fix it internally.

With my limited understanding of the code, it looks like to me there is no
protection against short reads in 2.0. But in 3.0, we seem to have some
short read transformation. At least, from comments it feels like that code
should have taken care of cases like this. So this must be a bug in 3.0
code, where as in 2.0 the complete feature for short read protection is
missing. Is my understanding right? Can you please shed more light on this?

I have created a JIRA as you asked -
https://issues.apache.org/jira/browse/CASSANDRA-12872

This is my first JIRA, so I don't know conventions to set priority. As its
data inconsistency issue, I believe this is critical. Feel free to change
the priority according to community conventions.

Thanks,
Bhaskar

On Wed, Nov 2, 2016 at 1:26 AM, Benjamin Lerer 
wrote:

> Hi Bhaskar,
>
> Thanks for reporting that problem. It is a nice catch :-)
>
> Could you open a JIRA ticket with all the information that you provided?
>
> I will try to fix that problem.
>
> Benjamin
>
>
> On Wed, Nov 2, 2016 at 12:00 AM, Bhaskar Muppana 
> wrote:
>
> > Hi Guys,
> >
> > We are seeing an issue with paging reads missing some small number of
> > columns when we do paging/limit reads. We get this on a single DC cluster
> > itself when both reads and writes are happening with QUORUM. Paging/limit
> > reads see this issue. I have attached the ccm based script which
> reproduces
> > the problem.
> >
> > * Keyspace RF - 2
> > * Table (id int, course text, marks int, primary key(id, course))
> > * replicas for partition key 1 - r1, r2 and r3
> > * insert (1, '1', 1) ,  (1, '2', 2),  (1, '3', 3),  (1, '4', 4),  (1,
> '5',
> > 5) - succeeded on all 3 replicas
> > * insert (1, '6', 6) succeeded on r1 and r3, failed on r2
> > * delete (1, '2'), (1, '3'), (1, '4'), (1, '5') succeeded on r1 and r2,
> > failed on r3
> > * insert (1, '7', 7) succeeded on r1 and r2, failed on r3
> >
> > Local data on 3 nodes looks like as below now
> >
> > r1: (1, '1', 1), tombstone(2-5 records), (1, '6', 6), (1, '7', 7)
> > r2: (1, '1', 1), tombstone(2-5 records), (1, '7', 7)
> > r3: (1, '1', 1),  (1, '2', 2),  (1, '3', 3),  (1, '4', 4),  (1, '5',
> > 5), (1, '6', 6)
> >
> > If we do a paging read with page_size 2, and if it gets data from r2 and
> > r3, then it will only get the data (1, '1', 1) and (1, '7', 7) skipping
> > record 6. This problem would happen if the same query is not doing paging
> > but limit set to 2 records.
> >
> > Resolution code for reads works same for paging queries and normal
> > queries. Co-ordinator shouldn't respond back to client with
> records/columns
> > that it didn't have complete visibility on all required replicas (in this
> > case 2 replicas). In above case, it is sending back record (1, '7', 7)
> back
> > to client, but its visibility on r3 is limited up to (1, '2', 2) and it
> is
> > relying on just r2 data to assume (1, '6', 6) doesn't exist, which is
> > wrong. End of the resolution all it can conclusively say any thing about
> is
> > (1, '1', 1), which exists and (1, '2', 2), which is deleted.
> >
> > Ideally we should have different resolution implementation for
> > paging/limit queries.
> >
> > We could reproduce this on 2.0.17, 2.1.16 and 3.0.9.
> >
> > Seems like 3.0.9 we have ShortReadProtection transformation on list
> > queries. I assume that is to protect against the cases like above. But,
> we
> > can reproduce the issue in 3.0.9 as well.
> >
> > Thanks,
> > Bhaskar
> >
> >
> >
> >
> >
> >
> >
>

Re: Many failing unit tests, prior to any changes. NoSuchFieldError: rpc_port

2016-11-02 Thread BORIS MELAMED

OK, I've created a new worktree. Did not create IDEA files there. Just ran
'ant', and then 'ant test', in a terminal window.
There, I'm not getting the 'java.lang.NoSuchFieldError: rpc_port' errors,
and only about 13 tests fail, some of them "crashing":

untitled text 9:1348: [junit] Testcase:
testStandardDirs(org.apache.cassandra.db.DirectoriesTest)FAILED
untitled text 9:1354: [junit] Test
org.apache.cassandra.db.DirectoriesTest FAILED
untitled text 9:1507: [junit] Test
org.apache.cassandra.db.RecoveryManagerFlushedTest FAILED (crashed)
untitled text 9:1526: [junit] Test
org.apache.cassandra.db.RecoveryManagerMissingHeaderTest FAILED (crashed)
untitled text 9:1545: [junit] Test
org.apache.cassandra.db.RecoveryManagerTest FAILED (crashed)
untitled text 9:1564: [junit] Test
org.apache.cassandra.db.RecoveryManagerTruncateTest FAILED (crashed)
untitled text 9:3422: [junit] Test
org.apache.cassandra.db.commitlog.CommitLogTest FAILED
untitled text 9:3459: [junit] Test
org.apache.cassandra.db.commitlog.CommitLogUpgradeTest FAILED
untitled text 9:3503: [junit] Test
org.apache.cassandra.db.commitlog.SegmentReaderTest FAILED
untitled text 9:4210: [junit] Testcase:
encryptedHints(org.apache.cassandra.hints.HintsEncryptionTest): FAILED
untitled text 9:4217: [junit] Test
org.apache.cassandra.hints.HintsEncryptionTest FAILED
untitled text 9:5055: [junit] Test
org.apache.cassandra.security.CipherFactoryTest FAILED
untitled text 9:5093: [junit] Test
org.apache.cassandra.security.EncryptionUtilsTest FAILED
untitled text 9:5275: [junit] Test
org.apache.cassandra.service.RemoveTest FAILED


*Boris Melamed*  |Software Engineer
*w:* ++972-545691126  *e: boris.mela...@weather.com
*
 
 
 

On Wed, Nov 2, 2016 at 4:23 PM, Licata, Christopher (CONT) <
christopher.lic...@capitalone.com> wrote:

> Yea, sorry.  I never got that many failing tests.  Perhaps it could be
> environment variable related.
>
> Thanks,
> Christopher Licata
> Senior Software Engineer
> Featureless Tech Monsters
> Card Rewards
> 718.916.8940
>
>
>
> On 11/2/16, 10:10 AM, "BORIS MELAMED"  wrote:
>
> Actually, 279 out of 296 failing tests seem to fail with this same
> error:
> java.lang.NoSuchFieldError: rpc_port
> at org.apache.cassandra.OffsetAwareConfigurationLoader.loadConfig(
> OffsetAwareConfigurationLoader.java:52)
>
>
>
>
> 
>
> The information contained in this e-mail is confidential and/or
> proprietary to Capital One and/or its affiliates and may only be used
> solely in performance of work or services for Capital One. The information
> transmitted herewith is intended only for use by the individual or entity
> to which it is addressed. If the reader of this message is not the intended
> recipient, you are hereby notified that any review, retransmission,
> dissemination, distribution, copying or other use of, or taking of any
> action in reliance upon this information is strictly prohibited. If you
> have received this communication in error, please contact the sender and
> delete the material from your computer.
>

Re: Bug in paging reads and limit reads (short reads!)

[GitHub] cassandra pull request #80: CASSANDRA-12869: Don't load mx4j beans twice

[GitHub] cassandra pull request #81: 12869 trunk

Re: Many failing unit tests, prior to any changes. NoSuchFieldError: rpc_port

Re: [VOTE] Release Apache Cassandra 3.0.10

Re: Many failing unit tests, prior to any changes. NoSuchFieldError: rpc_port

Re: Many failing unit tests, prior to any changes. NoSuchFieldError: rpc_port

Re: Many failing unit tests, prior to any changes. NoSuchFieldError: rpc_port

Re: [VOTE] Release Apache Cassandra 3.10

Re: [VOTE] Release Apache Cassandra 3.0.10

Re: Bug in paging reads and limit reads (short reads!)

Re: Many failing unit tests, prior to any changes. NoSuchFieldError: rpc_port

12 matches

Site Navigation

Mail list logo

Footer information