[ 
https://issues.apache.org/jira/browse/CASSANDRA-5510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13689618#comment-13689618
 ] 

Ryan McGuire commented on CASSANDRA-5510:
-----------------------------------------

[~bv5301], I'm trying to setup your java package in a local testing environment 
using [ccm|https://github.com/pcmanus/ccm].

I do this to create a 2x2 multi-dc setup:

{code}
ccm create -v 1.2.5 5510-test
ccm populate -n 2:2
ccm start
{code}

Then I load the DDL statements found in your README. Then I'm trying to get 
your java package to connect to that local cluster. I set the following in 
bootstrap.properties at the bottom:
{code}
##############################################################################
# Cassandra configuration
##############################################################################
GRM_CASSANDRA_CLUSTER_NAME=SCLD_CASS_INFRATEST
GRM_CASSANDRA_SEED_HOSTS=node1:7100,node3:7300
GRM_CASSANDRA_RPC_PORT=9160
GRM_LOCAL_DATACENTER=dc1
CASSANDRA_HOST_NAME=node1
{code}

However, I can't get it to go, I get this error when starting up:
{code}
java.lang.Exception: internal_error.cassandra.connect.detail
        at 
com.att.scld.cassandraDefect.util.CassandraConnectUtil.getHostToPin(CassandraConnectUtil.java:221)
        at 
com.att.scld.cassandraDefect.dao.RouteDAOImpl.deleteRoutes(RouteDAOImpl.java:165)
        at com.att.scld.cassandraDefect.Launcher.callCassandra(Launcher.java:66)
        at com.att.scld.cassandraDefect.Launcher.access$1(Launcher.java:62)
        at com.att.scld.cassandraDefect.Launcher$1.call(Launcher.java:37)
        at com.att.scld.cassandraDefect.Launcher$1.call(Launcher.java:1)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
        at java.util.concurrent.FutureTask.run(FutureTask.java:166)
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:722)
{code}

I believe this is telling me it can't connect to the cluster at all. This leads 
me to believe there is some setting in bootstrap.properties that I have wrong. 
Can you see if you can get your test to work against a local ccm cluster and 
also provide me with a new bootstrap.properties?

As an alternative to running your test, I created my own test. See 
delete_insert_test.py. I've tried to copy the general gist of what you're doing 
- creating some data, deleting part of it, reinserting it, and querying on a 
secondary index. So far I'm not able to reproduce the error using my test. To 
use my test, it needs to be copied to a [dtest 
environment|https://github.com/riptano/cassandra-dtest/blob/master/INSTALL.md] 
and run like 'nosetests delete_insert_test.py'
                
> Following sequence of operations delete, add, search by secondary index of 
> operations doesnot return correct results all the time.
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-5510
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5510
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.2, 1.2.5
>         Environment: Test
>            Reporter: Rao
>            Assignee: Ryan McGuire
>         Attachments: cassandra-analysis.zip
>
>
> Following sequence of operations delete, add, search by secondary index of 
> operations doesnot return correct results all the time.
> Performance tests was performed on the following sequence of operations: 
> delete a set of rows, add a set of rows and then search a set of rows by 
> secondary index by each thread. On search some of the rows were not returned 
> some times.
> configuration:
> replication_factor:2 per dc 
> nodes: 2 per dc
> consistency_level: local_quorum

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

Reply via email to