Thank you!
On Tue, 26 May 2015 15:45:01 -0500
Tyler Hobbs wrote:
> On Tue, May 26, 2015 at 2:00 PM, Eax Melanhovich wrote:
>
> >
> > First. Lets say I have a table (field1, field2, field3, field4),
> > where (field1, field2) is a primary key and field1 is partition
> > key. There is a secondar
Hello Graham,
> Are the CFs different, or all the same schema?
The column families are different. May be with better data modelling, we
can combine a few of them.
> Are you contractually obligated to actually separate data into separate
CFs?
No. Its just that we have several sub systems(around 10
Are the CFs different, or all the same schema? Are you contractually obligated
to actually separate data into separate CFs? It seems like you’d have a lot
simpler time if you could use the part of the partition key to separate data.
Note also, I don’t know what disks you are using, but disk cach
Good Day Everyone,
I am very happy with the (almost) linear scalability offered by C*. We had
a lot of problems with RDBMS.
But, I heard that C* has a limit on number of column families that can be
created in a single cluster.
The reason being each CF stores 1-2 MB on the JVM heap.
In our use ca
Hi -
As I understand, the Spark SQL Thrift/JDBC server cannot be used with the open
source C*. Only DSE supports the Spark SQL JDBC server.
We would like to find out whether how many organizations are using this
combination. If you do use DSE + Spark SQL JDBC server, it would be great if
you c
On Fri, May 15, 2015 at 2:32 AM, Rohit Naik
wrote:
> Apart from datastax java client driver, does Apache Cassandra provide
> its own java client driver? Or should be using the datastax one?
>
As a general statement, the Datastax drivers are the most well supported
clients.
=Rob
On Fri, May 15, 2015 at 8:39 AM, Ashic Mahtab wrote:
> I'm playing with DataStax's ODBC connector for Cassandra and have noticed
> something...well...broken.
>
> If I have a keyspace with tables that don't have a UDT column (even though
> the UDT is created), things work fine. However, the moment
On Tue, May 26, 2015 at 2:00 PM, Eax Melanhovich wrote:
>
> First. Lets say I have a table (field1, field2, field3, field4), where
> (field1, field2) is a primary key and field1 is partition key. There is
> a secondary index for field3 column. Do I right understand that in this
> case query like:
On Sun, May 17, 2015 at 9:59 PM, Anishek Agarwal wrote:
> Question: The Number of SST tables read, would it also include those where
> the bloom filter gave a false positive ? or is it just the number to
> actually do the reads.
>
It doesn't know the positive is false until it reads into the SST
On Tue, May 19, 2015 at 4:47 AM, Kaushal Shriyan
wrote:
> I am looking forward for your reply and please do let me know if you need
> any other additional information.
>
I might file a JIRA if I were you; your use case is an edge case which
might expose a bug.
=Rob
On Thu, May 21, 2015 at 6:04 AM, Ken Hancock
wrote:
> Is there any method to disable this programmatically on a table-by-table
> basis.
>
No, but I could imagine that feature being handy in some cases, perhaps
file a JIRA for it?
=Rob
On Tue, May 19, 2015 at 5:59 AM, Tzach Livyatan
wrote:
> My guess is system_traces initialization complete only after any data
> insertion.
> Before it does, any attempt to read from it either from nodetool, cqlsh
> or streaming to a new node will fail.
>
I would :
1) Check for this issue in i
Hello.
I'm reading "Beginning Apache Cassandra Development" and there are a few
things I can't figure out.
First. Lets say I have a table (field1, field2, field3, field4), where
(field1, field2) is a primary key and field1 is partition key. There is
a secondary index for field3 column. Do I right
@Sean -> You can manually change the ports used by Datastax agent using the
address.yaml file in the agent install directory.
+1 on using racks to separate it out... but it will increase operational
complexity somewhat
On 26 May 2015 at 08:11, Nate McCall wrote:
>
>> If you're running multiple
>
>
> If you're running multiple nodes on a single server, vnodes give you no
> control over which instance has which key (whereas you can assign initial
> tokens). Therefore you could have two of your three replicas on the same
> physical server which, if it goes down, you can't read or write at
You should not run a truncate until the whole ring is reporting
"Up/Normal." If there is a lot of flapping and it's a critical situation,
disable hinted handoff as well (and you may want to move
phi_convict_threshold up to 16 as well temporarily).
Stopping the compaction process temporarily on ea
>
> If I have a 20-node cluster with 2 nodes on each physical server, can I
> use 10 racks to properly segment my partitions?
>
>
Yes.
>
>
> On Sun, May 24, 2015 at 5:38 PM, Jonathan Haddad
> wrote:
>
>> What impact would vnodes have on strong consistency? I think the problem
>> you're describ
By default the cli will connect to localhost so you don't even need to
specify a host (-h). You should only need to specify a host if connecting
to a remote host or locally on a different ip than localhost (127.0.0.1).
Mark
On 26 May 2015 at 15:37, Mahmood Naderan wrote:
> Thanks. Instead of c
Hi Jean,
I am trying to solve a similar problem here. I would say that the only
deterministic way is to rebuild the SStable of that column family via
nodetool scrub.
Otherwise you'd need to :
* decrease tombstone_threshold
* wait for gc_grace_time
Cheers,
Stefano
On Tue, May 26, 2015 at 12:51
Thanks. Instead of changing cassandra.yaml parameters, I found that the default
is "localhost". So I ran "cassandra-cli -h localhost "
I will try the latest version. Thanks a lot.
Regards,
Mahmood
Hi Jason,
When the 3N cluster is up and running, I need to get the data from SN into
the 3N cluster and then give the SN server back. So I need to keep the
data, but on completely new servers – just trying to work out what the best
way of doing that is. The volume of data that needs migrating wo
will you add this lent one node into the 3N to form a cluster? but really ,
if you are just started, you could use this one node for your learning by
installing multiple instances for experiments or development purposes only.
imho, in the long run, this proove to be very valuable, as least for me.
Nate, how does this get around the issue? I'm guessing that just extends
the timeout, but if I had a server failure such that the server was down
for a couple hours, truncate would still have issues?
On Sat, May 23, 2015 at 5:46 PM, Nate McCall wrote:
> >
> > Truncate would have been the tool
I had the exact same question, but I think this is what Nate was thinking:
If you're running multiple nodes on a single server, vnodes give you no
control over which instance has which key (whereas you can assign initial
tokens). Therefore you could have two of your three replicas on the same
phy
Hi gurus,
We have ordered some hardware for a 3-node cluster, but its ETA is 6 to 8
weeks. In the meantime, I have been lent a single server that I can use. I
am wondering what the best way is to set up my single node (SN), so I can
then move to the 3-node cluster (3N) when the hardware arrives.
I played around with these settings, namely the tombstone_threshold, and it
**eventually** triggered a Tombstone Compaction.
Now I see that getting rid of these Tombstone is a process which takes some
times.
I would like to be able to schedule a Tombstone Compaction.
Is there a way to trigger i
Have you configured the rpc_address to listen on that ip? You can check
your nodes casandra.yaml for the rpc_address setting.
On a side node why are you testing on such an old version of Cassandra? The
latest versions of 1.2.x is 1.2.19. There are also two branches of 2.x
which are 2.0.15 and 2.1.
Hello,I have downloaded cassandra-1.2.0 for a test. The output of
./bin/cassandra and ./bin/cassandra-cli seems to be fine. Please see
http://pastebin.com/Tgs7qyjS
Next, I created a setup-ycsb.cql and wrote[mahmood@tiger ycsb-0.1.4]$ cat
setup-ycsb.cql
CREATE KEYSPACE usertable
with placement_st
I see, thanks Jason!
Can a dev confirm it is safe to apply those changes on live data? Also, if
I understood correctly, those parameters still obey the gc_grace_seconds,
that is, no compaction to evict tombstones will take place before
gc_grace_seconds elapsed, correct?
Cheers,
Stefano
On Tue, M
Hi,
Generally it can take a couple of seconds before a schema change has
propagated to all nodes. The schema will in most cases converge, but as far
as I've understood, concurrent schema changes are considered a bad practise
and can lead to inconsistent schemas down the road. IIRC if one executes
30 matches
Mail list logo
