cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Clint Kelly <>
Subject Re: Cassandra Chef cookbook - weird bug with broadcast_address:
Date Mon, 31 Mar 2014 15:32:07 GMT
Hi Marcin,

You are correct that I am using Vagrant.  Sorry for not specifying that.

OMG you are correct.  I spent about an hour over the weekend trying to
figure out what was going on.  I got confused because "listen_address"
is also set to node[:ipaddress], and listen_address was always set
correctly, but that is because it was set directly.  Oh my goodness.
Thanks for your help, this is really really embarrassing!

Best regards,

On Mon, Mar 31, 2014 at 8:27 AM, Marcin Cabaj <> wrote:
> Hi Clint,
> I'm guessing you are using vagrant. The thing is cassandra-chef-cookbook use
> template cassandra.yaml.erb, where you can find:
> "broadcast_address: <%= node[:cassandra][:broadcast_address] %>" which in
> turn is equal to "node[:ipaddress]".
> Value of node[:ipaddress] depends on how do you configure networking in
> vagrant/vbox, with default networking configuration node[:ipaddress] is
> equal hence your broadcast_address.
> You can setup networking in different way or setup attribute
> node[:cassandra][:broadcast_address] manually.
> On Mon, Mar 31, 2014 at 3:03 AM, Clint Kelly <> wrote:
>> All,
>> Has anyone used the Cassandra Chef cookbook
>> and seen
>> "broadcast_address:" in /etc/cassandra/cassandra.yaml?  I looked
>> through the source code for the cookbook and I have no idea how this is
>> happening.
>> I was able to fix this by just commenting out the broadcast_address in the
>> template for /etc/cassandra/cassanrda.yaml and moving on, but this is pretty
>> strange!
>> Best regards,
>> Clint

View raw message