Hi,
I have requirement to fetch million row as result of my query which is
giving timeout errors.
I am fetching results by selecting clustering columns, then why the queries
are taking so long. I can change the timeout settings but I need the data
to fetched faster as per my requirement.
My table
Sorry I gave you wrong table definition for query. Here a composite key
of image_caseid, x and uuid which is unique. I have used x in clustering
columns to query it. And used secondary index on y column.
1. Example
*cqlsh:images> CREATE TABLE images.results1 (uuid uuid,
analysis_execution_id varch
Yeah, you may have to add a dummy column populated with a constant, or just
pick some other additional column to index that you can apply = to. It's
just a requirement to assure that a filtered select isn't too-too slow.
Uh if you are applying = to your primary key then there is no need for
an
Hi,
In my case I am just trying to do range queries on 2 dimensions i.e. x and
y.
*cqlsh:images> CREATE TABLE images.results1 (uuid uuid,
analysis_execution_id varchar, analysis_execution_uuid uuid, x double, y
double, submit_date timestamp, points list, PRIMARY KEY
(image_caseid));*
With seco
In my case,i have:
UN *127.0.0.1* 83.05 KB 256 100.0%
460ddcd9-1ee8-48b8-a618-c076056aad07 rack1
i'd like to change the ip address like:
UN *192.168.1.4*
so i have to modify the file cassandra.yam
# Setting this to 0.0.0.0 is always wrong.
*listen_address: localhost*
-->
*listen_ad
On Mon, Mar 16, 2015 at 6:51 PM, Ben Bromhead wrote:
> If you are running a sequential repair (or have previously run a sequential
> repair that is still running) Cassandra will still have the file descriptors
> open for files in the snapshot it is using for the repair operation.
Yeah, that align
I'm using cassandra 2.1.2 and datastax cassandra-driver-core-2.1.2. Here is a
strange problem: when a keyspace is created ( or table created, deleted),
some of my clients received duplicated events, about 200+ times. my cluster and
my clients are in different places(not in one lan).
attach file
Lucene or Solr is better. I’m using lucene
> 在 2015年3月18日，上午2:11，Jack Krupansky 写道：
>
> 1. Create multiple secondary indexes, one for each non-key column you need to
> index on. Not recommended. Considered an anti-pattern for Cassandra.
> 2. Use DSE Search/Solr.
> 3. Use Lucene-based indexing wi
Yes, for over 2 years.
As for #2 - you would keep all CFs in both DCs. But, maybe only do RF=2 in OLTP
and 3 in reporting. Not sure of all your requirements. Writes are fast and
cheap in Cassandra, so I wouldn’t be concerned with “extra” writes in the OLTP
DC.
Sean Durity – Cassandra Admin, B
1. Create multiple secondary indexes, one for each non-key column you need
to index on. Not recommended. Considered an anti-pattern for Cassandra.
2. Use DSE Search/Solr.
3. Use Lucene-based indexing with TumpleJump/Stargate or Stratio.
-- Jack Krupansky
On Tue, Mar 17, 2015 at 1:49 PM, Mehak Meh
Hi,
I want to perform range queries (as in x and y ranges) on a large data
billions of rows.
CQL allows me to put Non EQ restrictions on only one of the clustering
columns.
Its not allowing me to filter the data using any other column even with use
of Allow Filtering option.
cqlsh:images> *select
Thanks Sean. Are you using 2 Cassandra instances on single node in PRODUCTION
environment?
Yes. We considered having separate virtual DC for OLTP and Reporting something
similar to the approach mentioned at
http://www.datastax.com/docs/datastax_enterprise3.1/solutions/dse_search_cluster
.
The
Hi,
I configured parameter as follows -
Gc_grace_seconds = 1hour.
Tombstone threshold = 1%
1. I deleted 33% of the existing data but I don't see any change in disk
space the next day (24 hrs). Column family had 24,000 rows and the number of
partition keys per row is about 1million. Is the
We run two cassandra nodes on the same host for a use case that requires a
random ordered ring and a byte ordered ring. It is technically feasible.
However, it makes administration of the rings a bit tougher (different ports
for one, etc.). OpsCenter agents can only connect to one of the rings a
i have to configure cassandra.yaml ? that's it ?
echo "INFORMATION:"
echo "Make changes to /etc/security/limits.d/cassandra.conf and
/etc/security/limits.conf manually as per
http://www.datastax.com/documentation/cassandra/2.0/cassandra/install/installRecommendSettings.html
."
echo "Remember to *
The script that you ran has a lot of comments with links that describe the
installation process. I would suggest reading those links.
On Tue, Mar 17, 2015 at 3:42 PM, jean paul wrote:
> Hello All,
>
> I launched the script (./cassandra-install.sh) without making any changes
> and it works.
> The
Hello All,
I launched the script (./cassandra-install.sh) without making any changes
and it works.
Then:
*First Terminal:*
$cassandra
...
INFO 10:52:26,655 Node /127.0.0.1 state jump to normal
INFO 10:52:26,791 Starting listening for CQL clients on
localhost/127.0.0.1:9042...
Yes we see https://issues.apache.org/jira/browse/CASSANDRA-8716 in our
testing
Thanks
Ajay
On Tue, Mar 17, 2015 at 3:20 PM, Marcus Eriksson wrote:
> Do you see the segfault or do you see
> https://issues.apache.org/jira/browse/CASSANDRA-8716 ?
>
> On Tue, Mar 17, 2015 at 10:34 AM, Ajay wrote:
Hello, thanks a lot for your help :)
i try to find answers to these questions:
*Second Terminal:*
$nodetool join
This node has already joined the ring.
$nodetool status
Datacenter: datacenter1
===
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- AddressLoad
Hello All,
I launched the script (./cassandra-install.sh) without making any changes
and it works.
Then:
*First Terminal:*
$cassandra
...
INFO 10:52:26,655 Node /127.0.0.1 state jump to normal
INFO 10:52:26,791 Starting listening for CQL clients on
localhost/127.0.0.1:9042...
Do you see the segfault or do you see
https://issues.apache.org/jira/browse/CASSANDRA-8716 ?
On Tue, Mar 17, 2015 at 10:34 AM, Ajay wrote:
> Hi,
>
> Now that 2.0.13 is out, I don't see nodetool cleanup issue(
> https://issues.apache.org/jira/browse/CASSANDRA-8718) been fixed yet. The
> bug show
Hi,
Now that 2.0.13 is out, I don't see nodetool cleanup issue(
https://issues.apache.org/jira/browse/CASSANDRA-8718) been fixed yet. The
bug show priority Minor. Anybody facing this issue?.
Thanks
Ajay
On Thu, Mar 12, 2015 at 11:41 PM, Robert Coli wrote:
> On Thu, Mar 12, 2015 at 10:50 AM, Aj
Yeah, Cassandra nodes are peer oriented. The meta data are recorded in “system
tables”.
There are 6 nodes in my single dc cluster; Is meta data recorded in all the
nodes’ “system tables” after executing “create table” statement?
How to guarantee the meta-data are recorded in all nodes?
Should I
Oops, my bad. Not "master node" I meant "system tables". Cassandra has no
master nodes, it is entirely peer oriented. I apologize profusely, and hope
I have not confused.
*...*
*“Life should not be a journey to the grave with the intention of arriving
safely in apretty and well prese
24 matches
Mail list logo
