.0.0.1=dc-test:my-notebook
>
> On Mon, Jun 11, 2012 at 1:49 PM, Carlo Pires wrote:
> > Just installed cassandra 1.1.1 and run:
> >
> > root@carlo-laptop:/tmp# cassandra-cli -h localhost
> > Connected to: "Test Cluster" on localhost/9160
> > Welcome
at org.apache.cassandra.cli.CliMain.main(CliMain.java:346)
[default@accounts] root@carlo-laptop:/tmp#
root@carlo-laptop:/tmp# cat /etc/cassandra/cassandra-topology.properties
127.0.0.1:dc-test:my-notebook
root@carlo-laptop:/tmp#
I did not find anything relevant in JIRA. The setup is a single instance
cassandra in my notebook running the default cassandra 1.1.1 of debian repo.
--
Carlo Pires
s the compareTo of java.util.UUID as a reference:
>>>>
>>>> public int compareTo(UUID val) {
>>>>// The ordering is intentionally set up so that the UUIDs
>>>>// can simply be numerically compared as two numbers
>>>>return (this.mostSigBits < val.mostSigBits ? -1 :
>>>>(this.mostSigBits > val.mostSigBits ? 1 :
>>>> (this.leastSigBits < val.leastSigBits ? -1 :
>>>> (this.leastSigBits > val.leastSigBits ? 1 :
>>>> 0;
>>>> }
>>>>
>>>>
>>>
>>>
>>> --
>>> Tyler Hobbs
>>> DataStax <http://datastax.com/>
>>>
>>>
>>>
>>
>>
>> --
>> Tyler Hobbs
>> DataStax <http://datastax.com/>
>>
>>
>>
>
>
> --
> Tyler Hobbs
> DataStax <http://datastax.com/>
>
>
>
--
Carlo Pires
62 8209-1444 TIM
62 3251-1383
Skype: carlopires
family, as it causes an exception.
>
> Is there a way to force the schema propagation through the thrift API (not
> the CLI)?
>
> Thanks in advance.
>
> --
> Regards,
>
> Tharindu
>
> blog: http://mackiemathew.com/
>
>
--
Carlo Pires
62 8209-1444 TIM
62 3251-1383
Skype: carlopires
I'm not in production yet. As exercise, stopped all nodes when this error
occurred and I could not start any node again.
If you need to use composite types and create/drop column families on the
fly you must be prepared to instabilities.
I found out this is related to schema change. Happens *every time* I create
drop and new CF with composite types. As workaround I:
* never stop all nodes together
To stop a node:
* repair and compact a node before stopping it
* stop and start it again
* if it started fine good if not, remove all
t;> thank you.
>>
>
> As far as I can see, this may raise memory requirements for you, since you
> need to have index/bloom filter for each column family in memory.
>
> --
> Best regards,
> Vitalii Tymchyshyn
>
--
Carlo Pires
62 8209-1444 TIM
62 3251-1383
Skype: carlopires
Hi,
I can't start a node of my cluster. Could someone help me to catch the
problem?
Using: debian with cassandra 1.0.6.
root@carlo-laptop:/etc/cassandra# cat /var/log/cassandra/output.log
INFO 13:46:00,596 JVM vendor/version: Java HotSpot(TM) 64-Bit Server
VM/1.6.0_26
INFO 13:46:00,600 Heap si
