Question about the way that isLocalDc() gets local DC
I have a C* sourcecode related question: Can someone explain me why isLocalDc() in OutboundTcpConnection class uses DatabaseDescriptor.getRpcAddress() for retrieving "local" IP, instead of using DD.getListenAddress() or - even better - FBUtilities.getLocalAddress()? I mean - I don't get why RPC address is checked before initializing internode (so not RPC-based) communication, which will use IP address returned by (in OTCPool) FBUtilities.getLocalAddress()? Do I miss something here? Kind regards, Michał
Re: Question about the way that isLocalDc() gets local DC
Sure, done :-) https://issues.apache.org/jira/browse/CASSANDRA-5299 MM W dniu 28.02.2013 15:30, Marcus Eriksson pisze: that should probably be FBUtilities.getBroadCastAddress even, could you file a ticket?
Re: PasswordAuthenticator
Don't you have a default "cassandra" user in system_auth.users? cqlsh> SELECT * from system_auth.users ; name | super ---+--- cassandra | True It should be created on startup and you should see this in your logs: "PasswordAuthenticator created default user cassandra" However, if it fails, you should see this: "Skipped default superuser setup: some nodes were not ready" Do you have any of these messages in your log? M. W dniu 05.06.2013 17:19, Michael Hanl pisze: Hello, Based on several examples online I was trying to use the PasswordAuthenticator on our project nodes. Although setting it up with the version 1.2.5 of cassandra was not that difficult, I cannot seem to get access neither in cqlsh nor in the CLI. Having a look at the filesystem and the schema tables (nodetool) that the respective column families have been created with the startup of cassandra, but there is no default user, which of course I need to setup my own users. I tried several repairs with the nodetool already, but obviously when there are no data in the column family, repair is kind of useless. I hope someone has an idea (besides writing my own authentiction interface implementation). Kind regards, Michael Hanl
How to check the last commit that Cassandra release was built on?
Hi, Let's say I want to use Cassandra's Git repository to build my own Cassandra .deb file which is _exactely_ the same as specified release (for example: cassandra-1.1) and apply there some patches of my choice. Could you please explain me how can I check which commit should I pick to do it properly? I think that there's an easy way to check it, but - unluckily - I don't know it (I'm not very familiar with git) or I miss something. I was expecting something like a tag or so, but I can't find anything that will make me sure that I found the commit I was looking for. Of course I can check tags, but they don't look like they are up-to-date... michal@aperture:~/workspace/cassandra-trunk$ git status # On branch cassandra-1.1 (...) michal@aperture:~/workspace/cassandra-trunk$ git describe cassandra-1.1.0-beta1-529-g8b81c8f (beta1?!) I know I can check debian/changelog for the last "New Release" message and then find/guess the appropriate commit basing on author, date/time and commit message, but I don't think it's the best approach ;) -- Kind regards, Michał
Re: How to check the last commit that Cassandra release was built on?
Thanks for help ;) It seems it was obvious, but I got completely misguided by "git describe" - it should return the most recent tag name and I was (I am?) confused why it returns the "beta1" one... Michał W dniu 07.05.2012 15:41, Jonathan Ellis pisze: $ git tag ... cassandra-1.0.9 cassandra-1.1.0 cassandra-1.1.0-beta1 cassandra-1.1.0-beta2 cassandra-1.1.0-rc1 ... $ git checkout cassandra-1.1.0 On Mon, May 7, 2012 at 8:28 AM, Michal Michalski wrote: Hi, Let's say I want to use Cassandra's Git repository to build my own Cassandra .deb file which is _exactely_ the same as specified release (for example: cassandra-1.1) and apply there some patches of my choice. Could you please explain me how can I check which commit should I pick to do it properly? I think that there's an easy way to check it, but - unluckily - I don't know it (I'm not very familiar with git) or I miss something. I was expecting something like a tag or so, but I can't find anything that will make me sure that I found the commit I was looking for. Of course I can check tags, but they don't look like they are up-to-date... michal@aperture:~/workspace/cassandra-trunk$ git status # On branch cassandra-1.1 (...) michal@aperture:~/workspace/cassandra-trunk$ git describe cassandra-1.1.0-beta1-529-g8b81c8f (beta1?!) I know I can check debian/changelog for the last "New Release" message and then find/guess the appropriate commit basing on author, date/time and commit message, but I don't think it's the best approach ;) -- Kind regards, Michał
