oli wrote:
> On Wed, Dec 11, 2013 at 1:35 AM, Sven Stark wrote:
>
>> thanks for replying. Could you please be a bit more specific, though. Eg
>> what exactly is being compacted - there is/was no data at all in the
>> cluster save for a few hundred kB in the system CF (see
to identify the inconsistencies. So
> there is quite a bit of streaming which you see as your network traffic.
>
> Rahul
>
>
> On Wed, Dec 11, 2013 at 11:02 AM, Sven Stark
> wrote:
>
>> Corollary:
>>
>> what is getting shipped over the wire? The ganglia screensh
127.67 KB 256 32.4%
bd6b2059-e9dc-4b01-95ab-d7c4fc0ec639 rack1
UN 10.1.2.12 107.62 KB 256 34.7%
5258f178-b20e-408f-a7bf-b6da2903e026 rack1
Much appreciated.
Sven
On Wed, Dec 11, 2013 at 3:56 PM, Sven Stark wrote:
> Howdy!
>
> Not a matter of life or death, just curious.
Howdy!
Not a matter of life or death, just curious.
I've just stood up a three node cluster (v1.2.8) on three c3.2xlarge boxes
in AWS. Silly me forgot the correct replication factor for one of the
needed keyspaces. So I changed it via cli and ran a nodetool repair.
Well .. there is no data at all
bug
> should be fixed in the next release of OpsCenter.
>
> Nick
>
>
> On Wed, Oct 16, 2013 at 8:07 PM, Sven Stark wrote:
>
>> Hi guys,
>>
>> we have secured C* jmx with username/pw. We upgraded our Opscenter from
>> 3.0.2 to 3.2.2 last week and no
Hi guys,
we have secured C* jmx with username/pw. We upgraded our Opscenter from
3.0.2 to 3.2.2 last week and noticed that the agents could not connect
anymore
ERROR [jmx-metrics-4] 2013-10-17 00:45:54,437 Error getting general metrics
java.lang.SecurityException: Authentication failed! Credentia
