Make sure you've got ntpd running, otherwise this will be an ongoing nightmare.
On Thu, Jul 3, 2014 at 5:00 PM, Sávio S. Teles de Oliveira
wrote:
> I have synchronized the clocks and works!
>
>
> 2014-07-03 20:58 GMT-03:00 Sávio S. Teles de Oliveira
> :
>
>>> Did you make sure all the nodes are o
I have synchronized the clocks and works!
2014-07-03 20:58 GMT-03:00 Sávio S. Teles de Oliveira <
savio.te...@cuia.com.br>:
> Did you make sure all the nodes are on the same time? If they're not,
>> you'll get some weird results.
>
>
> They were not on the same time. I've synchronized the time
>
> Did you make sure all the nodes are on the same time? If they're not,
> you'll get some weird results.
They were not on the same time. I've synchronized the time and works!
Tks
2014-07-03 16:58 GMT-03:00 Jack Krupansky :
> You said that the updates do show up eventually – how long does
You said that the updates do show up eventually – how long does it take?
-- Jack Krupansky
From: Sávio S. Teles de Oliveira
Sent: Thursday, July 3, 2014 1:30 PM
To: user@cassandra.apache.org
Subject: Re: Write Inconsistency to update a row
Are you sure all the nodes are working at that time?
thank you for the replies; I am rethinking the schema design, one possible
solution is to "implode" one dimension and get N times less CFs.
With this approach I would come up with (cql) tables with up to 100
columns; would that be a problem?
Thank You,
Tommaso
2014-07-02 23:43 GMT+02:00 Jack Kru
The Cassandra team is pleased to announce the release of Apache Cassandra
version 1.2.18.
Cassandra is a highly scalable second-generation distributed database,
bringing together Dynamo's fully distributed design and Bigtable's
ColumnFamily-based data model. You can read more here:
http://cassan
Did you make sure all the nodes are on the same time? If they're not,
you'll get some weird results.
On Thu, Jul 3, 2014 at 10:30 AM, Sávio S. Teles de Oliveira
wrote:
>> Are you sure all the nodes are working at that time?
>
>
> Yes. They are working.
>
>> I would suggest increasing the replica
>
> Are you sure all the nodes are working at that time?
Yes. They are working.
I would suggest increasing the replication factor (for example 3) and use
> CL=ALL or QUORUM to find out what is going wrong.
I did! I still have the same problem.
2014-07-03 13:40 GMT-03:00 Panagiotis Garefalak
This is one of the trickier areas of doing multi dc. The current
recommendation is to use a separate message queue.
If you'd like to see remote triggers, you could fire a JIRA. Get back
to the list w/ the ticket #, I'm sure there are others who have
similar needs.
On Thu, Jul 3, 2014 at 10:04 A
Triggers only execute on the local coordinator. I would also not
recommend using them.
On Thu, Jul 3, 2014 at 9:58 AM, Robert Coli wrote:
> On Thu, Jul 3, 2014 at 4:41 AM, Bèrto ëd Sèra
> wrote:
>>
>> Now the question: is there any way to use triggers so that they will
>> locally index data fro
On Thu, Jul 3, 2014 at 4:41 AM, Bèrto ëd Sèra
wrote:
> Now the question: is there any way to use triggers so that they will
> locally index data from remote DCs when it comes in?
>
As I understand it, you probably should not use triggers in production in
their current form.
=Rob
This seems like a hinted handoff issue but since you use CL = ONE it should
happen.
Are you sure all the nodes are working at that time? You could use nodetool
status to check that.
I would suggest increasing the replication factor (for example 3) and use
CL=ALL or QUORUM to find out what is going
replication_factor=1
CL=ONE
Does the data show up eventually?
Yes.
Can be the clocks?
2014-07-03 10:47 GMT-03:00 graham sanderson :
> What is your keyspace replication_factor?
>
> What consistency level are you reading/writing with?
>
> Does the data show up eventually?
>
> I’m assuming you d
What is your keyspace replication_factor?
What consistency level are you reading/writing with?
Does the data show up eventually?
I’m assuming you don’t have any errors (timeouts etc) on the write site
On Jul 3, 2014, at 7:55 AM, Sávio S. Teles de Oliveira
wrote:
> I have two Cassandra 2.0.5
I have two Cassandra 2.0.5 servers running with some datas inserted, where
each row have one empty column. When the client send a lot of update
commands to fill this column in each row, some lines update their content,
but some lines remain with the empty column.
Using one server, this never happe
Hi all,
we are planning a set of 3 data-centres (each located in a different
continent). There is a possibility that the connection among them will
occasionally fail for an unforeseeable length of time. The quorum would be
limited to the local data-centre, as each user access his local
data-centre
You can have a look here:
https://github.com/Netflix/astyanax/wiki/Chunked-Object-Store
On Thu, Jul 3, 2014 at 11:05 AM, Akshay Ballarpure <
akshay.ballarp...@tcs.com> wrote:
> Hello Team,
> I am going to use Cassandra DB in our existing project as its suiting my
> requirement.
> I have binary f
Hello Team,
I am going to use Cassandra DB in our existing project as its suiting my
requirement.
I have binary files generated from our application every one minutes and
have to store them in DB.
I have a table which is having 100+ column on which customer is going to
use only 10 column for se
18 matches
Mail list logo
