Hi Phil,
just my 2 cents, just watch out for these issues like counter type
(replicate on write), compaction (when node load goes huge) and cassandra
instance gc. This issues exists in 1.x perhaps it has been resolved in 2.x.
hth
jason
On Mon, Dec 1, 2014 at 10:44 PM, Matt Brown wrote:
> This
I don’t know what it is but I also saw “empty” keyspaces via CQL while
migrating an existing test cluster from 2.0.9 to 2.1.0 (final release bits
prior to labelling). Since I was doing this manually (and had cqlsh problems
due to python change) I figured it might have been me.
My observation w
As a a test, I took down a node, deleted /var/lib/cassandra and restarted it.
After it joined the cluster, it’s about 75% the size of its neighbors (both in
terms of bytes and numbers of keys). Prior to my test it was approximately the
same size. I have no explanation for why that node would shr
On Tue, Dec 2, 2014 at 12:21 PM, Robert Wille wrote:
> As a a test, I took down a node, deleted /var/lib/cassandra and restarted
> it. After it joined the cluster, it’s about 75% the size of its neighbors
> (both in terms of bytes and numbers of keys). Prior to my test it was
> approximately the
On Mon, Dec 1, 2014 at 11:07 PM, Jason Wee wrote:
> Hi Rob, any recommended documentation on describing
> explanation/configuration of the JVM heap and permanent generation ? We
> stucked in this same situation too. :(
>
The archives of this list are chock full of explorations of various cases.
On Mon, Dec 1, 2014 at 7:10 PM, Neha Trivedi wrote:
> No the old node is not defective. We Just want to separate out that Server
> for testing.
> And add a new node. (Present cluster has two Nodes and RF=2)
>
If you currently have two nodes and RF=2, you must add the new node before
removing the
I meant to mention that I had run repair, but neglected to do so. Sorry about
that. Repair runs pretty quick (a fraction of the time that compaction takes)
and doesn’t seem to do anything.
On Dec 2, 2014, at 1:44 PM, Robert Coli
mailto:rc...@eventbrite.com>> wrote:
On Tue, Dec 2, 2014 at 12:21
Hi all -
Just getting started setting up OpsCenter today. I have a 3 node cassandra
cluster and (afaict) the agent installed and running happily on all 3
nodes. I also have OpsCenter up and running on a 4th node. I do not have
SSL enabled between these nodes.
In the OpsCenter interface, I see
On Tue, Dec 2, 2014 at 1:06 PM, Robert Wille wrote:
> I meant to mention that I had run repair, but neglected to do so. Sorry
> about that. Repair runs pretty quick (a fraction of the time that
> compaction takes) and doesn’t seem to do anything.
>
If repair doesn't find differing ranges, your
On Tue, Dec 2, 2014 at 2:21 PM, Robert Wille wrote:
> As a a test, I took down a node, deleted /var/lib/cassandra and restarted
> it.
Did you decommission or removenode it when you took it down? If you
didn't, the "old" node is still in the ring, and affects the replication.
--
Tyler Hobbs
I have observed this kind of situation with 0 agents connected. Restarting
the agents always helped so far. By the way, check the agent's logs and
opscenterd logs, there may be some clues there.
On Tue, Dec 2, 2014 at 4:59 PM, Ian Rose wrote:
> Hi all -
>
> Just getting started setting up OpsCen
I didn’t do anything except kill the server process, delete /var/lib/cassandra,
and start it back up again. nodetool status shows all nodes as UN, and doesn’t
display any unexpected nodes.
I don’t know if this sheds any light on the issue, but I’ve added a
considerable amount of data to the clu
Hi,
Is it possible to save columns of collection types (Map in particular) with the
Spark connector? I see that you can easily read a collection column, but i
can’t find any documentation on writing such columns.
mn
Often this is caused by the agent version not matching the OpsCenter
version. Unfortunately the UI currently reports a version mismatch as 'not
installed'. Can you check the versions of your OpsCenter and agent installs?
On Tue, Dec 2, 2014 at 5:06 PM, Nikolai Grigoriev
wrote:
> I have observed
Hi,
We have a cluster (2.0.11) of 6 nodes (RF=3), c3.4xlarge instances, about
50 column families. Cassandra heap takes 8GB out of the 30GB of every
instance.
We mainly store time series-like data, where each data point is a binary
blob of 5-20KB. We use wide rows, and try to put in the same row a
Thanks Jens and Robert !!!
On Wed, Dec 3, 2014 at 2:20 AM, Robert Coli wrote:
> On Mon, Dec 1, 2014 at 7:10 PM, Neha Trivedi
> wrote:
>
>> No the old node is not defective. We Just want to separate out that
>> Server for testing.
>> And add a new node. (Present cluster has two Nodes and RF=2)
>
Hi ALL,
There is a grogram to consume messages from queue; according to the message,
the program will READ a row and then UPDATE the row;
BUT, sometimes, the UPDATE statement is fail, the result of READ statement is
also the old content before UDPATE.
Any suggestions from you are appreciated.
Th
ack and many thanks for the tips and help..
jason
On Wed, Dec 3, 2014 at 4:49 AM, Robert Coli wrote:
> On Mon, Dec 1, 2014 at 11:07 PM, Jason Wee wrote:
>
>> Hi Rob, any recommended documentation on describing
>> explanation/configuration of the JVM heap and permanent generation ? We
>> stucke
The system setting is as the following:
Cluster replication:
replication = {'class': 'NetworkTopologyStrategy', 'GTA_SZ_DC1':2}
Totally, 5 Nodes,
OS of Nodes are windows.
Thanks & Regards,
鄢来琼 / Peter YAN, Staff Software Engineer,
A3 Dept., GTA Information Technology Co., Ltd.
19 matches
Mail list logo
