Re: Installing Cassandra from Tarball

[Steve Anderson]

I think you’re right Tyler; the warning does not appear after making the 
changes suggested by Bhuvan.

Steve
—
"Surely, those who believe, those who are Jewish, the Christians, and the 
converts; anyone who (1) believes in God, (2) believes in the Last Day, and (3) 
leads a righteous life, will receive their recompense from their Lord; they 
have nothing to fear, nor will they grieve." (Quran 2:62, 5:69) …learn more at 
www.masjidtucson.org


> On 15/06/2016, at 12:26 AM, Tyler Hobbs  wrote:
> 
> 
> On Mon, Jun 13, 2016 at 11:49 AM, Bhuvan Rawal  > wrote:
> 
> WARN  15:41:58 Cassandra server running in degraded mode. Is swap disabled? : 
> true,  Address space adequate? : true,  nofile limit adequate? : false, nproc 
> limit adequate? : false
> You need to disable swap in order to avoid this message, using swap space can 
> have serious performance implications. Make sure you disable fstab entry as 
> well for swap partition.
> 
> It looks like swap is actually disabled, but the nofile and nproc limits are 
> too low.
> 
> 
> -- 
> Tyler Hobbs
> DataStax 

Re: Installing Cassandra from Tarball

[Steve Anderson]

Awesone, thanks Bhuvan! 

I have not worried about the JMX warning at this stage.

There were two other warnings, but I assume these are due to the size of my 
Amazon Linux Image (and are not worth worrying about at this stage).

WARN  17:24:20 Small commitlog volume detected at /var/lib/cassandra/commitlog; 
setting commitlog_total_space_in_mb to 1983.  You can override this in 
cassandra.yaml

WARN  17:24:20 Only 5.809GiB free across all data volumes. Consider adding more 
capacity to your cluster or removing obsolete snapshots

Regarding the commitlog_total_space_in_mb property, I see from the 
cassandra.yaml file:

The default value is the smaller of 8192, and 1/4 of the total space of 
the commitlog volume.

Awesome, thanks again.

Steve
—
"Surely, those who believe, those who are Jewish, the Christians, and the 
converts; anyone who (1) believes in God, (2) believes in the Last Day, and (3) 
leads a righteous life, will receive their recompense from their Lord; they 
have nothing to fear, nor will they grieve." (Quran 2:62, 5:69) …learn more at 
www.masjidtucson.org


> On 14/06/2016, at 12:49 AM, Bhuvan Rawal  wrote:
> 
> 
> Hi Steve,
> 
> Please find the responses in line:
> 
> WARN  15:41:58 Unable to lock JVM memory (ENOMEM). This can result in part of 
> the JVM being swapped out, especially with mmapped I/O enabled. Increase 
> RLIMIT_MEMLOCK or run Cassandra as root.
>  You can edit - /etc/security/limits.conf and put these lines in there
> 
> * - memlock unlimited
> * - nofile 10
> * - nproc 32768
> * - as unlimited
> 
> and reload the properties by command $ sudo sysctl -p
> and then checking it :
> $ ulimit -l
> and for the cassandra process by :
> $ cat /proc//limits
> Source - Datastax Troubleshooting 
> 
> 
> WARN  15:41:58 jemalloc shared library could not be preloaded to speed up 
> memory allocations
> If you want to allocate off heap memory using jemalloc then uncomment this 
> line in cassandra-env.sh and provide appropriate jemalloc path
> JVM_OPTS="$JVM_OPTS -Djava.library.path=/lib/"
> 
> WARN  15:41:58 JMX is not enabled to receive remote connections. Please see 
> cassandra-env.sh for more info.
> By default JMX is enabled only for local connections, if you want to debug 
> from a remote machine mark LOCAL_JMX=no  in cassandra-env.sh
> 
> WARN  15:41:58 Cassandra server running in degraded mode. Is swap disabled? : 
> true,  Address space adequate? : true,  nofile limit adequate? : false, nproc 
> limit adequate? : false
> You need to disable swap in order to avoid this message, using swap space can 
> have serious performance implications. Make sure you disable fstab entry as 
> well for swap partition.
> 
> Thanks & Regards,
> Bhuvan
> 

Re: Installing Cassandra from Tarball

[Tyler Hobbs]

On Mon, Jun 13, 2016 at 11:49 AM, Bhuvan Rawal  wrote:

>
> WARN  15:41:58 Cassandra server running in degraded mode. Is swap
>> disabled? : true,  Address space adequate? : true,  nofile limit adequate?
>> : false, nproc limit adequate? : false
>>
> You need to disable swap in order to avoid this message, using swap space
> can have serious performance implications. Make sure you disable fstab
> entry as well for swap partition.
>

It looks like swap is actually disabled, but the nofile and nproc limits
are too low.


-- 
Tyler Hobbs
DataStax 

Re: Installing Cassandra from Tarball

[Bhuvan Rawal]

Hi Steve,

Please find the responses in line:

WARN  15:41:58 Unable to lock JVM memory (ENOMEM). This can result in part
> of the JVM being swapped out, especially with mmapped I/O enabled. Increase
> RLIMIT_MEMLOCK or run Cassandra as root.
>
 You can edit -* /etc/security/limits.conf *and put these lines in there

* - memlock unlimited
* - nofile 10
* - nproc 32768
* - as unlimited

and reload the properties by command $ sudo sysctl -p
and then checking it :
$ ulimit -l
and for the cassandra process by :
$ cat /proc//limits
Source - Datastax Troubleshooting


WARN  15:41:58 jemalloc shared library could not be preloaded to speed up
> memory allocations
>
If you want to allocate off heap memory using jemalloc then uncomment this
line in *cassandra-env.sh* and provide appropriate jemalloc path
JVM_OPTS="$JVM_OPTS -Djava.library.path=/lib/"

WARN  15:41:58 JMX is not enabled to receive remote connections. Please see
> cassandra-env.sh for more info.
>
By default JMX is enabled only for local connections, if you want to debug
from a remote machine mark LOCAL_JMX=no  in *cassandra-env.sh*

WARN  15:41:58 Cassandra server running in degraded mode. Is swap disabled?
> : true,  Address space adequate? : true,  nofile limit adequate? : false,
> nproc limit adequate? : false
>
You need to disable swap in order to avoid this message, using swap space
can have serious performance implications. Make sure you disable fstab
entry as well for swap partition.

Thanks & Regards,
Bhuvan

Re: installing cassandra

[Ryan Svihla]

TLDR
Can I suggest as a good middle road to at least use something like csshx
https://code.google.com/p/csshx/ ?

Details

Having worked with a huge variety of skill sets and cluster sizes, I'd
argue "it depends" a lot on team skills, especially when problems occur.

Point being even with small clusters when you're figuring out how to setup
and tune nodes people frequently get it wrong the first few times (almost
invariably not following the docs), and then are trying to fix problems in
prod while not making another mistake in the process, under pressure. This
is a wonderfully combination to screw up even more.

I lean towards tools to automate things (classic bash scripting in my case)
but I was synchronizing configuration 15 years ago, and not doing things by
hand even then.

On Mon, Dec 22, 2014 at 9:44 AM, Eric Stevens  wrote:
>
> If you're just trying to get your feet wet with distributed software, and
> your node count is going to be reasonably low and won't grow any time soon,
> it's probably easier to just install it yourself rather than trying to also
> learn how to use software deployment technologies like puppet or chef.
> Those aren't easier until you are operating at a scale where you need to be
> able to automate adding new nodes.
>
>
> On Sun, Dec 21, 2014, 8:05 AM Ryan Svihla  wrote:
>
>> Puppet, Chef, Ansible and I'm sure many others. I've personally worked
>> with a number of people on all three, a quick google for "Puppet Cassandra"
>> will give you a large number of examples and modules just for Puppet and
>> Cassandra.
>>
>> On Sat, Dec 20, 2014 at 2:01 PM, Adaryl "Bob" Wakefield, MBA <
>> adaryl.wakefi...@hotmail.com> wrote:
>>>
>>>   I have a three node cluster that I’m using to learn how to work with
>>> disturbed software. There is this thing called Puppet that helps you with
>>> deploying software. Can/should I use Puppet to install Cassandra on my
>>> cluster or is there some sort of built in network wide deployment in the
>>> install process already?
>>>
>>> B.
>>>
>>
>>
>> --
>>
>> [image: datastax_logo.png] 
>>
>> Ryan Svihla
>>
>> Solution Architect
>>
>> [image: twitter.png]  [image: linkedin.png]
>> 
>>
>> DataStax is the fastest, most scalable distributed database technology,
>> delivering Apache Cassandra to the world’s most innovative enterprises.
>> Datastax is built to be agile, always-on, and predictably scalable to any
>> size. With more than 500 customers in 45 countries, DataStax is the
>> database technology and transactional backbone of choice for the worlds
>> most innovative companies such as Netflix, Adobe, Intuit, and eBay.
>>
>>

-- 

[image: datastax_logo.png] 

Ryan Svihla

Solution Architect

[image: twitter.png]  [image: linkedin.png]


DataStax is the fastest, most scalable distributed database technology,
delivering Apache Cassandra to the world’s most innovative enterprises.
Datastax is built to be agile, always-on, and predictably scalable to any
size. With more than 500 customers in 45 countries, DataStax is the
database technology and transactional backbone of choice for the worlds
most innovative companies such as Netflix, Adobe, Intuit, and eBay.

Re: installing cassandra

[Eric Stevens]

If you're just trying to get your feet wet with distributed software, and
your node count is going to be reasonably low and won't grow any time soon,
it's probably easier to just install it yourself rather than trying to also
learn how to use software deployment technologies like puppet or chef.
Those aren't easier until you are operating at a scale where you need to be
able to automate adding new nodes.

On Sun, Dec 21, 2014, 8:05 AM Ryan Svihla  wrote:

> Puppet, Chef, Ansible and I'm sure many others. I've personally worked
> with a number of people on all three, a quick google for "Puppet Cassandra"
> will give you a large number of examples and modules just for Puppet and
> Cassandra.
>
> On Sat, Dec 20, 2014 at 2:01 PM, Adaryl "Bob" Wakefield, MBA <
> adaryl.wakefi...@hotmail.com> wrote:
>>
>>   I have a three node cluster that I’m using to learn how to work with
>> disturbed software. There is this thing called Puppet that helps you with
>> deploying software. Can/should I use Puppet to install Cassandra on my
>> cluster or is there some sort of built in network wide deployment in the
>> install process already?
>>
>> B.
>>
>
>
> --
>
> [image: datastax_logo.png] 
>
> Ryan Svihla
>
> Solution Architect
>
> [image: twitter.png]  [image: linkedin.png]
> 
>
> DataStax is the fastest, most scalable distributed database technology,
> delivering Apache Cassandra to the world’s most innovative enterprises.
> Datastax is built to be agile, always-on, and predictably scalable to any
> size. With more than 500 customers in 45 countries, DataStax is the
> database technology and transactional backbone of choice for the worlds
> most innovative companies such as Netflix, Adobe, Intuit, and eBay.
>
>

Re: installing cassandra

[Ryan Svihla]

Puppet, Chef, Ansible and I'm sure many others. I've personally worked with
a number of people on all three, a quick google for "Puppet Cassandra" will
give you a large number of examples and modules just for Puppet and
Cassandra.

On Sat, Dec 20, 2014 at 2:01 PM, Adaryl "Bob" Wakefield, MBA <
adaryl.wakefi...@hotmail.com> wrote:
>
>   I have a three node cluster that I’m using to learn how to work with
> disturbed software. There is this thing called Puppet that helps you with
> deploying software. Can/should I use Puppet to install Cassandra on my
> cluster or is there some sort of built in network wide deployment in the
> install process already?
>
> B.
>


-- 

[image: datastax_logo.png] 

Ryan Svihla

Solution Architect

[image: twitter.png]  [image: linkedin.png]


DataStax is the fastest, most scalable distributed database technology,
delivering Apache Cassandra to the world’s most innovative enterprises.
Datastax is built to be agile, always-on, and predictably scalable to any
size. With more than 500 customers in 45 countries, DataStax is the
database technology and transactional backbone of choice for the worlds
most innovative companies such as Netflix, Adobe, Intuit, and eBay.

Re: Installing Cassandra Multinode on CentOs coming up with exception

[Vineet Mishra]

Hey Patricia,

Thanks for your kind response. I will surely take care of that provided the
use of virtual nodes.

Thanks again!


On Tue, Aug 26, 2014 at 10:42 PM, Patricia Gorla  wrote:

> Vineet,
>
> One more thing -- you have initial_token and num_tokens both set. If you
> are trying to use virtual nodes, you should comment out initial_token as
> this setting overrides num_tokens.
>
> Cheers,
>
>
> On Tue, Aug 26, 2014 at 5:39 AM, Vineet Mishra 
> wrote:
>
>> Thanks Vivek!
>>
>> It was indeed a formatting issue in yaml, got it work!
>>
>>
>> On Tue, Aug 26, 2014 at 6:06 PM, Vivek Mishra 
>> wrote:
>>
>>> Please read about http://www.yaml.org/start.html.
>>> Looks like formatting issue. You might be missing/adding incorrect spaces
>>>
>>> Validate your YAML file. This should help you out
>>> http://yamllint.com/
>>>
>>> -Vivek
>>>
>>>
>>> On Tue, Aug 26, 2014 at 4:20 PM, Vineet Mishra 
>>> wrote:
>>>
 Hi Mark,

 Yes I was generating my own cassandra.yaml with the configuration
 mentioned below,

 cluster_name: 'node'
 initial_token: 0
 num_tokens: 256
 seed_provider:
 - class_name: org.apache.cassandra.locator.SimpleSeedProvider
 parameters:
 - seeds: "192.168.1.32"
 listen_address: 192.168.1.32
 rpc_address: 0.0.0.0
 endpoint_snitch: RackInferringSnitch

 Similarly for second node

 cluster_name: 'node'
 initial_token: 2305843009213693952
 num_tokens: 256
 seed_provider:
 - class_name: org.apache.cassandra.locator.SimpleSeedProvider
 parameters:
 - seeds: "192.168.1.32"
 listen_address: 192.168.1.36
 rpc_address: 0.0.0.0
 endpoint_snitch: RackInferringSnitch

 and so on. . .



 But even if I use default xml with the necessary configurational
 changes I am getting following error.

  INFO 16:13:38,225 Loading settings from
 file:/home/cluster/cassandra/conf/cassandra.yaml
 ERROR 16:13:38,301 Fatal configuration error
 org.apache.cassandra.exceptions.ConfigurationException: Invalid yaml
  at
 org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:100)
 at
 org.apache.cassandra.config.DatabaseDescriptor.loadConfig(DatabaseDescriptor.java:135)
  at
 org.apache.cassandra.config.DatabaseDescriptor.(DatabaseDescriptor.java:111)
 at
 org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:156)
  at
 org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:496)
 at
 org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:585)
 Caused by: while parsing a block mapping
  in 'reader', line 10, column 2:
  cluster_name: 'node'
  ^
 expected , but found BlockMappingStart
  in 'reader', line 30, column 3:
   initial_token: 0
   ^

 at
 org.yaml.snakeyaml.parser.ParserImpl$ParseBlockMappingKey.produce(ParserImpl.java:570)
  at org.yaml.snakeyaml.parser.ParserImpl.peekEvent(ParserImpl.java:158)
 at org.yaml.snakeyaml.parser.ParserImpl.checkEvent(ParserImpl.java:143)
  at
 org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:230)
 at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:159)
  at
 org.yaml.snakeyaml.composer.Composer.composeDocument(Composer.java:122)
 at org.yaml.snakeyaml.composer.Composer.getSingleNode(Composer.java:105)
  at
 org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:120)
 at org.yaml.snakeyaml.Yaml.loadFromReader(Yaml.java:481)
  at org.yaml.snakeyaml.Yaml.loadAs(Yaml.java:475)
 at
 org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:93)
  ... 5 more
 Invalid yaml

 Could you figure out whats making the yaml invalid.

 Thanks!


 On Tue, Aug 26, 2014 at 4:06 PM, Mark Reddy 
 wrote:

> You are missing commitlog_sync in your cassandra.yaml.
>
> Are you generating your own cassandra.yaml or editing the package
> default? If you are generating your own there are several configuration
> options that are required and if not present, Cassandra will fail to
> start.
>
>
> Regards,
> Mark
>
>
> On 26 August 2014 11:14, Vineet Mishra  wrote:
>
>> Thanks Mark,
>> That was indeed yaml formatting issue.
>> Moreover I am getting the underlying error now,
>>
>> INFO 15:33:43,770 Loading settings from
>> file:/home/cluster/cassandra/conf/cassandra.yaml
>>  INFO 15:33:44,100 Data files directories: [/var/lib/cassandra/data]
>>  INFO 15:33:44,101 Commit log directory: /var/lib/cassandra/commitlog
>> ERROR 15:33:44,103 Fatal configuration error
>> org.apache.cassandra.exceptions.ConfigurationException: Missing
>> required directive CommitLogSync
>>  

Re: Installing Cassandra Multinode on CentOs coming up with exception

[Patricia Gorla]

Vineet,

One more thing -- you have initial_token and num_tokens both set. If you
are trying to use virtual nodes, you should comment out initial_token as
this setting overrides num_tokens.

Cheers,


On Tue, Aug 26, 2014 at 5:39 AM, Vineet Mishra 
wrote:

> Thanks Vivek!
>
> It was indeed a formatting issue in yaml, got it work!
>
>
> On Tue, Aug 26, 2014 at 6:06 PM, Vivek Mishra 
> wrote:
>
>> Please read about http://www.yaml.org/start.html.
>> Looks like formatting issue. You might be missing/adding incorrect spaces
>>
>> Validate your YAML file. This should help you out
>> http://yamllint.com/
>>
>> -Vivek
>>
>>
>> On Tue, Aug 26, 2014 at 4:20 PM, Vineet Mishra 
>> wrote:
>>
>>> Hi Mark,
>>>
>>> Yes I was generating my own cassandra.yaml with the configuration
>>> mentioned below,
>>>
>>> cluster_name: 'node'
>>> initial_token: 0
>>> num_tokens: 256
>>> seed_provider:
>>> - class_name: org.apache.cassandra.locator.SimpleSeedProvider
>>> parameters:
>>> - seeds: "192.168.1.32"
>>> listen_address: 192.168.1.32
>>> rpc_address: 0.0.0.0
>>> endpoint_snitch: RackInferringSnitch
>>>
>>> Similarly for second node
>>>
>>> cluster_name: 'node'
>>> initial_token: 2305843009213693952
>>> num_tokens: 256
>>> seed_provider:
>>> - class_name: org.apache.cassandra.locator.SimpleSeedProvider
>>> parameters:
>>> - seeds: "192.168.1.32"
>>> listen_address: 192.168.1.36
>>> rpc_address: 0.0.0.0
>>> endpoint_snitch: RackInferringSnitch
>>>
>>> and so on. . .
>>>
>>>
>>>
>>> But even if I use default xml with the necessary configurational changes
>>> I am getting following error.
>>>
>>>  INFO 16:13:38,225 Loading settings from
>>> file:/home/cluster/cassandra/conf/cassandra.yaml
>>> ERROR 16:13:38,301 Fatal configuration error
>>> org.apache.cassandra.exceptions.ConfigurationException: Invalid yaml
>>>  at
>>> org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:100)
>>> at
>>> org.apache.cassandra.config.DatabaseDescriptor.loadConfig(DatabaseDescriptor.java:135)
>>>  at
>>> org.apache.cassandra.config.DatabaseDescriptor.(DatabaseDescriptor.java:111)
>>> at
>>> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:156)
>>>  at
>>> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:496)
>>> at
>>> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:585)
>>> Caused by: while parsing a block mapping
>>>  in 'reader', line 10, column 2:
>>>  cluster_name: 'node'
>>>  ^
>>> expected , but found BlockMappingStart
>>>  in 'reader', line 30, column 3:
>>>   initial_token: 0
>>>   ^
>>>
>>> at
>>> org.yaml.snakeyaml.parser.ParserImpl$ParseBlockMappingKey.produce(ParserImpl.java:570)
>>>  at org.yaml.snakeyaml.parser.ParserImpl.peekEvent(ParserImpl.java:158)
>>> at org.yaml.snakeyaml.parser.ParserImpl.checkEvent(ParserImpl.java:143)
>>>  at
>>> org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:230)
>>> at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:159)
>>>  at
>>> org.yaml.snakeyaml.composer.Composer.composeDocument(Composer.java:122)
>>> at org.yaml.snakeyaml.composer.Composer.getSingleNode(Composer.java:105)
>>>  at
>>> org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:120)
>>> at org.yaml.snakeyaml.Yaml.loadFromReader(Yaml.java:481)
>>>  at org.yaml.snakeyaml.Yaml.loadAs(Yaml.java:475)
>>> at
>>> org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:93)
>>>  ... 5 more
>>> Invalid yaml
>>>
>>> Could you figure out whats making the yaml invalid.
>>>
>>> Thanks!
>>>
>>>
>>> On Tue, Aug 26, 2014 at 4:06 PM, Mark Reddy 
>>> wrote:
>>>
 You are missing commitlog_sync in your cassandra.yaml.

 Are you generating your own cassandra.yaml or editing the package
 default? If you are generating your own there are several configuration
 options that are required and if not present, Cassandra will fail to
 start.


 Regards,
 Mark


 On 26 August 2014 11:14, Vineet Mishra  wrote:

> Thanks Mark,
> That was indeed yaml formatting issue.
> Moreover I am getting the underlying error now,
>
> INFO 15:33:43,770 Loading settings from
> file:/home/cluster/cassandra/conf/cassandra.yaml
>  INFO 15:33:44,100 Data files directories: [/var/lib/cassandra/data]
>  INFO 15:33:44,101 Commit log directory: /var/lib/cassandra/commitlog
> ERROR 15:33:44,103 Fatal configuration error
> org.apache.cassandra.exceptions.ConfigurationException: Missing
> required directive CommitLogSync
>  at
> org.apache.cassandra.config.DatabaseDescriptor.applyConfig(DatabaseDescriptor.java:147)
> at
> org.apache.cassandra.config.DatabaseDescriptor.(DatabaseDescriptor.java:111)
>  at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:156)
> at
> org.apache.cassandra.service.CassandraDaemon

Re: Installing Cassandra Multinode on CentOs coming up with exception

[Vineet Mishra]

Thanks Vivek!

It was indeed a formatting issue in yaml, got it work!


On Tue, Aug 26, 2014 at 6:06 PM, Vivek Mishra  wrote:

> Please read about http://www.yaml.org/start.html.
> Looks like formatting issue. You might be missing/adding incorrect spaces
>
> Validate your YAML file. This should help you out
> http://yamllint.com/
>
> -Vivek
>
>
> On Tue, Aug 26, 2014 at 4:20 PM, Vineet Mishra 
> wrote:
>
>> Hi Mark,
>>
>> Yes I was generating my own cassandra.yaml with the configuration
>> mentioned below,
>>
>> cluster_name: 'node'
>> initial_token: 0
>> num_tokens: 256
>> seed_provider:
>> - class_name: org.apache.cassandra.locator.SimpleSeedProvider
>> parameters:
>> - seeds: "192.168.1.32"
>> listen_address: 192.168.1.32
>> rpc_address: 0.0.0.0
>> endpoint_snitch: RackInferringSnitch
>>
>> Similarly for second node
>>
>> cluster_name: 'node'
>> initial_token: 2305843009213693952
>> num_tokens: 256
>> seed_provider:
>> - class_name: org.apache.cassandra.locator.SimpleSeedProvider
>> parameters:
>> - seeds: "192.168.1.32"
>> listen_address: 192.168.1.36
>> rpc_address: 0.0.0.0
>> endpoint_snitch: RackInferringSnitch
>>
>> and so on. . .
>>
>>
>>
>> But even if I use default xml with the necessary configurational changes
>> I am getting following error.
>>
>>  INFO 16:13:38,225 Loading settings from
>> file:/home/cluster/cassandra/conf/cassandra.yaml
>> ERROR 16:13:38,301 Fatal configuration error
>> org.apache.cassandra.exceptions.ConfigurationException: Invalid yaml
>>  at
>> org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:100)
>> at
>> org.apache.cassandra.config.DatabaseDescriptor.loadConfig(DatabaseDescriptor.java:135)
>>  at
>> org.apache.cassandra.config.DatabaseDescriptor.(DatabaseDescriptor.java:111)
>> at
>> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:156)
>>  at
>> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:496)
>> at
>> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:585)
>> Caused by: while parsing a block mapping
>>  in 'reader', line 10, column 2:
>>  cluster_name: 'node'
>>  ^
>> expected , but found BlockMappingStart
>>  in 'reader', line 30, column 3:
>>   initial_token: 0
>>   ^
>>
>> at
>> org.yaml.snakeyaml.parser.ParserImpl$ParseBlockMappingKey.produce(ParserImpl.java:570)
>>  at org.yaml.snakeyaml.parser.ParserImpl.peekEvent(ParserImpl.java:158)
>> at org.yaml.snakeyaml.parser.ParserImpl.checkEvent(ParserImpl.java:143)
>>  at
>> org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:230)
>> at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:159)
>>  at
>> org.yaml.snakeyaml.composer.Composer.composeDocument(Composer.java:122)
>> at org.yaml.snakeyaml.composer.Composer.getSingleNode(Composer.java:105)
>>  at
>> org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:120)
>> at org.yaml.snakeyaml.Yaml.loadFromReader(Yaml.java:481)
>>  at org.yaml.snakeyaml.Yaml.loadAs(Yaml.java:475)
>> at
>> org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:93)
>>  ... 5 more
>> Invalid yaml
>>
>> Could you figure out whats making the yaml invalid.
>>
>> Thanks!
>>
>>
>> On Tue, Aug 26, 2014 at 4:06 PM, Mark Reddy 
>> wrote:
>>
>>> You are missing commitlog_sync in your cassandra.yaml.
>>>
>>> Are you generating your own cassandra.yaml or editing the package
>>> default? If you are generating your own there are several configuration
>>> options that are required and if not present, Cassandra will fail to
>>> start.
>>>
>>>
>>> Regards,
>>> Mark
>>>
>>>
>>> On 26 August 2014 11:14, Vineet Mishra  wrote:
>>>
 Thanks Mark,
 That was indeed yaml formatting issue.
 Moreover I am getting the underlying error now,

 INFO 15:33:43,770 Loading settings from
 file:/home/cluster/cassandra/conf/cassandra.yaml
  INFO 15:33:44,100 Data files directories: [/var/lib/cassandra/data]
  INFO 15:33:44,101 Commit log directory: /var/lib/cassandra/commitlog
 ERROR 15:33:44,103 Fatal configuration error
 org.apache.cassandra.exceptions.ConfigurationException: Missing
 required directive CommitLogSync
  at
 org.apache.cassandra.config.DatabaseDescriptor.applyConfig(DatabaseDescriptor.java:147)
 at
 org.apache.cassandra.config.DatabaseDescriptor.(DatabaseDescriptor.java:111)
  at
 org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:156)
 at
 org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:496)
  at
 org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:585)
 Missing required directive CommitLogSync
 Fatal configuration error; unable to start. See log for stacktrace.

 Do you have any idea about this.

 Thanks!


 On Tue, Aug 26, 2014 at 3:07 PM, Mark Reddy 
 wrote:

> It is telling

Re: Installing Cassandra Multinode on CentOs coming up with exception

[Vivek Mishra]

Please read about http://www.yaml.org/start.html.
Looks like formatting issue. You might be missing/adding incorrect spaces

Validate your YAML file. This should help you out
http://yamllint.com/

-Vivek


On Tue, Aug 26, 2014 at 4:20 PM, Vineet Mishra 
wrote:

> Hi Mark,
>
> Yes I was generating my own cassandra.yaml with the configuration
> mentioned below,
>
> cluster_name: 'node'
> initial_token: 0
> num_tokens: 256
> seed_provider:
> - class_name: org.apache.cassandra.locator.SimpleSeedProvider
> parameters:
> - seeds: "192.168.1.32"
> listen_address: 192.168.1.32
> rpc_address: 0.0.0.0
> endpoint_snitch: RackInferringSnitch
>
> Similarly for second node
>
> cluster_name: 'node'
> initial_token: 2305843009213693952
> num_tokens: 256
> seed_provider:
> - class_name: org.apache.cassandra.locator.SimpleSeedProvider
> parameters:
> - seeds: "192.168.1.32"
> listen_address: 192.168.1.36
> rpc_address: 0.0.0.0
> endpoint_snitch: RackInferringSnitch
>
> and so on. . .
>
>
>
> But even if I use default xml with the necessary configurational changes I
> am getting following error.
>
>  INFO 16:13:38,225 Loading settings from
> file:/home/cluster/cassandra/conf/cassandra.yaml
> ERROR 16:13:38,301 Fatal configuration error
> org.apache.cassandra.exceptions.ConfigurationException: Invalid yaml
>  at
> org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:100)
> at
> org.apache.cassandra.config.DatabaseDescriptor.loadConfig(DatabaseDescriptor.java:135)
>  at
> org.apache.cassandra.config.DatabaseDescriptor.(DatabaseDescriptor.java:111)
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:156)
>  at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:496)
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:585)
> Caused by: while parsing a block mapping
>  in 'reader', line 10, column 2:
>  cluster_name: 'node'
>  ^
> expected , but found BlockMappingStart
>  in 'reader', line 30, column 3:
>   initial_token: 0
>   ^
>
> at
> org.yaml.snakeyaml.parser.ParserImpl$ParseBlockMappingKey.produce(ParserImpl.java:570)
>  at org.yaml.snakeyaml.parser.ParserImpl.peekEvent(ParserImpl.java:158)
> at org.yaml.snakeyaml.parser.ParserImpl.checkEvent(ParserImpl.java:143)
>  at
> org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:230)
> at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:159)
>  at
> org.yaml.snakeyaml.composer.Composer.composeDocument(Composer.java:122)
> at org.yaml.snakeyaml.composer.Composer.getSingleNode(Composer.java:105)
>  at
> org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:120)
> at org.yaml.snakeyaml.Yaml.loadFromReader(Yaml.java:481)
>  at org.yaml.snakeyaml.Yaml.loadAs(Yaml.java:475)
> at
> org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:93)
>  ... 5 more
> Invalid yaml
>
> Could you figure out whats making the yaml invalid.
>
> Thanks!
>
>
> On Tue, Aug 26, 2014 at 4:06 PM, Mark Reddy 
> wrote:
>
>> You are missing commitlog_sync in your cassandra.yaml.
>>
>> Are you generating your own cassandra.yaml or editing the package
>> default? If you are generating your own there are several configuration
>> options that are required and if not present, Cassandra will fail to
>> start.
>>
>>
>> Regards,
>> Mark
>>
>>
>> On 26 August 2014 11:14, Vineet Mishra  wrote:
>>
>>> Thanks Mark,
>>> That was indeed yaml formatting issue.
>>> Moreover I am getting the underlying error now,
>>>
>>> INFO 15:33:43,770 Loading settings from
>>> file:/home/cluster/cassandra/conf/cassandra.yaml
>>>  INFO 15:33:44,100 Data files directories: [/var/lib/cassandra/data]
>>>  INFO 15:33:44,101 Commit log directory: /var/lib/cassandra/commitlog
>>> ERROR 15:33:44,103 Fatal configuration error
>>> org.apache.cassandra.exceptions.ConfigurationException: Missing required
>>> directive CommitLogSync
>>>  at
>>> org.apache.cassandra.config.DatabaseDescriptor.applyConfig(DatabaseDescriptor.java:147)
>>> at
>>> org.apache.cassandra.config.DatabaseDescriptor.(DatabaseDescriptor.java:111)
>>>  at
>>> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:156)
>>> at
>>> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:496)
>>>  at
>>> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:585)
>>> Missing required directive CommitLogSync
>>> Fatal configuration error; unable to start. See log for stacktrace.
>>>
>>> Do you have any idea about this.
>>>
>>> Thanks!
>>>
>>>
>>> On Tue, Aug 26, 2014 at 3:07 PM, Mark Reddy 
>>> wrote:
>>>
 It is telling you that your yaml is invalid, from looking at the
 snippet you have provided it looks like the seed_provider.parameters is not
 correctly indented, it should look something like:

 seed_provider:
   - class_name: org.apache.cassandra.locator.SimpleSeedProvide

Re: Installing Cassandra Multinode on CentOs coming up with exception

[Vineet Mishra]

Hi Mark,

Yes I was generating my own cassandra.yaml with the configuration mentioned
below,

cluster_name: 'node'
initial_token: 0
num_tokens: 256
seed_provider:
- class_name: org.apache.cassandra.locator.SimpleSeedProvider
parameters:
- seeds: "192.168.1.32"
listen_address: 192.168.1.32
rpc_address: 0.0.0.0
endpoint_snitch: RackInferringSnitch

Similarly for second node

cluster_name: 'node'
initial_token: 2305843009213693952
num_tokens: 256
seed_provider:
- class_name: org.apache.cassandra.locator.SimpleSeedProvider
parameters:
- seeds: "192.168.1.32"
listen_address: 192.168.1.36
rpc_address: 0.0.0.0
endpoint_snitch: RackInferringSnitch

and so on. . .



But even if I use default xml with the necessary configurational changes I
am getting following error.

 INFO 16:13:38,225 Loading settings from
file:/home/cluster/cassandra/conf/cassandra.yaml
ERROR 16:13:38,301 Fatal configuration error
org.apache.cassandra.exceptions.ConfigurationException: Invalid yaml
at
org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:100)
at
org.apache.cassandra.config.DatabaseDescriptor.loadConfig(DatabaseDescriptor.java:135)
at
org.apache.cassandra.config.DatabaseDescriptor.(DatabaseDescriptor.java:111)
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:156)
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:496)
at
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:585)
Caused by: while parsing a block mapping
 in 'reader', line 10, column 2:
 cluster_name: 'node'
 ^
expected , but found BlockMappingStart
 in 'reader', line 30, column 3:
  initial_token: 0
  ^

at
org.yaml.snakeyaml.parser.ParserImpl$ParseBlockMappingKey.produce(ParserImpl.java:570)
at org.yaml.snakeyaml.parser.ParserImpl.peekEvent(ParserImpl.java:158)
at org.yaml.snakeyaml.parser.ParserImpl.checkEvent(ParserImpl.java:143)
at
org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:230)
at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:159)
at org.yaml.snakeyaml.composer.Composer.composeDocument(Composer.java:122)
at org.yaml.snakeyaml.composer.Composer.getSingleNode(Composer.java:105)
at
org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:120)
at org.yaml.snakeyaml.Yaml.loadFromReader(Yaml.java:481)
at org.yaml.snakeyaml.Yaml.loadAs(Yaml.java:475)
at
org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:93)
... 5 more
Invalid yaml

Could you figure out whats making the yaml invalid.

Thanks!


On Tue, Aug 26, 2014 at 4:06 PM, Mark Reddy  wrote:

> You are missing commitlog_sync in your cassandra.yaml.
>
> Are you generating your own cassandra.yaml or editing the package default?
> If you are generating your own there are several configuration options that
> are required and if not present, Cassandra will fail to start.
>
>
> Regards,
> Mark
>
>
> On 26 August 2014 11:14, Vineet Mishra  wrote:
>
>> Thanks Mark,
>> That was indeed yaml formatting issue.
>> Moreover I am getting the underlying error now,
>>
>> INFO 15:33:43,770 Loading settings from
>> file:/home/cluster/cassandra/conf/cassandra.yaml
>>  INFO 15:33:44,100 Data files directories: [/var/lib/cassandra/data]
>>  INFO 15:33:44,101 Commit log directory: /var/lib/cassandra/commitlog
>> ERROR 15:33:44,103 Fatal configuration error
>> org.apache.cassandra.exceptions.ConfigurationException: Missing required
>> directive CommitLogSync
>>  at
>> org.apache.cassandra.config.DatabaseDescriptor.applyConfig(DatabaseDescriptor.java:147)
>> at
>> org.apache.cassandra.config.DatabaseDescriptor.(DatabaseDescriptor.java:111)
>>  at
>> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:156)
>> at
>> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:496)
>>  at
>> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:585)
>> Missing required directive CommitLogSync
>> Fatal configuration error; unable to start. See log for stacktrace.
>>
>> Do you have any idea about this.
>>
>> Thanks!
>>
>>
>> On Tue, Aug 26, 2014 at 3:07 PM, Mark Reddy 
>> wrote:
>>
>>> It is telling you that your yaml is invalid, from looking at the snippet
>>> you have provided it looks like the seed_provider.parameters is not
>>> correctly indented, it should look something like:
>>>
>>> seed_provider:
>>>   - class_name: org.apache.cassandra.locator.SimpleSeedProvider
>>> parameters:
>>>  - seeds: "192.168.1.32"
>>>
>>>
>>> Regards,
>>> Mark
>>>
>>>
>>> On 26 August 2014 08:12, Vineet Mishra  wrote:
>>>

 Hi All,

 I am installing Cassandra Multinode Setup on a 4 node CentOs Cluster,
 my cassandra.yaml looks like so

 cluster_name: 'node'
 initial_token: 0
 num_tokens: 256
 seed_provider:
 - class_name: org.apache.cassandra.locator.SimpleSeedProvider
 parameters:
 - seeds:

Re: Installing Cassandra Multinode on CentOs coming up with exception

[Mark Reddy]

You are missing commitlog_sync in your cassandra.yaml.

Are you generating your own cassandra.yaml or editing the package default?
If you are generating your own there are several configuration options that
are required and if not present, Cassandra will fail to start.


Regards,
Mark


On 26 August 2014 11:14, Vineet Mishra  wrote:

> Thanks Mark,
> That was indeed yaml formatting issue.
> Moreover I am getting the underlying error now,
>
> INFO 15:33:43,770 Loading settings from
> file:/home/cluster/cassandra/conf/cassandra.yaml
>  INFO 15:33:44,100 Data files directories: [/var/lib/cassandra/data]
>  INFO 15:33:44,101 Commit log directory: /var/lib/cassandra/commitlog
> ERROR 15:33:44,103 Fatal configuration error
> org.apache.cassandra.exceptions.ConfigurationException: Missing required
> directive CommitLogSync
>  at
> org.apache.cassandra.config.DatabaseDescriptor.applyConfig(DatabaseDescriptor.java:147)
> at
> org.apache.cassandra.config.DatabaseDescriptor.(DatabaseDescriptor.java:111)
>  at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:156)
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:496)
>  at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:585)
> Missing required directive CommitLogSync
> Fatal configuration error; unable to start. See log for stacktrace.
>
> Do you have any idea about this.
>
> Thanks!
>
>
> On Tue, Aug 26, 2014 at 3:07 PM, Mark Reddy 
> wrote:
>
>> It is telling you that your yaml is invalid, from looking at the snippet
>> you have provided it looks like the seed_provider.parameters is not
>> correctly indented, it should look something like:
>>
>> seed_provider:
>>   - class_name: org.apache.cassandra.locator.SimpleSeedProvider
>> parameters:
>>  - seeds: "192.168.1.32"
>>
>>
>> Regards,
>> Mark
>>
>>
>> On 26 August 2014 08:12, Vineet Mishra  wrote:
>>
>>>
>>> Hi All,
>>>
>>> I am installing Cassandra Multinode Setup on a 4 node CentOs Cluster, my
>>> cassandra.yaml looks like so
>>>
>>> cluster_name: 'node'
>>> initial_token: 0
>>> num_tokens: 256
>>> seed_provider:
>>> - class_name: org.apache.cassandra.locator.SimpleSeedProvider
>>> parameters:
>>> - seeds: "192.168.1.32"
>>> listen_address: 192.168.1.32
>>> rpc_address: 0.0.0.0
>>> endpoint_snitch: RackInferringSnitch
>>>
>>> Similarly cassandra.yaml for second node
>>>
>>> cluster_name: 'node'
>>> initial_token: 2305843009213693952
>>> num_tokens: 256
>>> seed_provider:
>>> - class_name: org.apache.cassandra.locator.SimpleSeedProvider
>>> parameters:
>>> - seeds: "192.168.1.32"
>>> listen_address: 192.168.1.36
>>> rpc_address: 0.0.0.0
>>> endpoint_snitch: RackInferringSnitch
>>>
>>> and so on. . .
>>>
>>> While trying to start the Server running on the Seed node(192.168.1.32)
>>> it throws this nasty exception and didn't start,
>>>
>>>
>>> -bash-4.1$ sudo bin/cassandra
>>>
>>> -bash-4.1$  INFO 12:19:46,653 Logging initialized
>>>  INFO 12:19:46,688 Loading settings from
>>> file:/home/cluster/cassandra/conf/cassandra.yaml
>>> ERROR 12:19:46,985 Fatal configuration error
>>> org.apache.cassandra.exceptions.ConfigurationException: Invalid yaml
>>>  at
>>> org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:100)
>>> at
>>> org.apache.cassandra.config.DatabaseDescriptor.loadConfig(DatabaseDescriptor.java:135)
>>>  at
>>> org.apache.cassandra.config.DatabaseDescriptor.(DatabaseDescriptor.java:111)
>>> at
>>> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:156)
>>>  at
>>> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:496)
>>> at
>>> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:585)
>>> Caused by: Can't construct a java object for 
>>> tag:yaml.org,2002:org.apache.cassandra.config.Config;
>>> exception=Cannot create property=seed_provider for
>>> JavaBean=org.apache.cassandra.config.Config@676c6370;
>>> java.lang.reflect.InvocationTargetException
>>>  in 'reader', line 1, column 1:
>>> cluster_name: 'pcross'
>>> ^
>>>
>>> at
>>> org.yaml.snakeyaml.constructor.Constructor$ConstructYamlObject.construct(Constructor.java:333)
>>>  at
>>> org.yaml.snakeyaml.constructor.BaseConstructor.constructObject(BaseConstructor.java:182)
>>> at
>>> org.yaml.snakeyaml.constructor.BaseConstructor.constructDocument(BaseConstructor.java:141)
>>>  at
>>> org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:127)
>>> at org.yaml.snakeyaml.Yaml.loadFromReader(Yaml.java:481)
>>>  at org.yaml.snakeyaml.Yaml.loadAs(Yaml.java:475)
>>> at
>>> org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:93)
>>>  ... 5 more
>>> Caused by: org.yaml.snakeyaml.error.YAMLException: Cannot create
>>> property=seed_provider for
>>> JavaBean=org.apache.cassandra.config.Config@676c6370;
>>> java.lang.reflect.InvocationTargetException
>>>  at
>>> org.yaml.snakeyaml.c

Re: Installing Cassandra Multinode on CentOs coming up with exception

[Vineet Mishra]

Thanks Mark,
That was indeed yaml formatting issue.
Moreover I am getting the underlying error now,

INFO 15:33:43,770 Loading settings from
file:/home/cluster/cassandra/conf/cassandra.yaml
 INFO 15:33:44,100 Data files directories: [/var/lib/cassandra/data]
 INFO 15:33:44,101 Commit log directory: /var/lib/cassandra/commitlog
ERROR 15:33:44,103 Fatal configuration error
org.apache.cassandra.exceptions.ConfigurationException: Missing required
directive CommitLogSync
at
org.apache.cassandra.config.DatabaseDescriptor.applyConfig(DatabaseDescriptor.java:147)
at
org.apache.cassandra.config.DatabaseDescriptor.(DatabaseDescriptor.java:111)
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:156)
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:496)
at
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:585)
Missing required directive CommitLogSync
Fatal configuration error; unable to start. See log for stacktrace.

Do you have any idea about this.

Thanks!


On Tue, Aug 26, 2014 at 3:07 PM, Mark Reddy  wrote:

> It is telling you that your yaml is invalid, from looking at the snippet
> you have provided it looks like the seed_provider.parameters is not
> correctly indented, it should look something like:
>
> seed_provider:
>   - class_name: org.apache.cassandra.locator.SimpleSeedProvider
> parameters:
>  - seeds: "192.168.1.32"
>
>
> Regards,
> Mark
>
>
> On 26 August 2014 08:12, Vineet Mishra  wrote:
>
>>
>> Hi All,
>>
>> I am installing Cassandra Multinode Setup on a 4 node CentOs Cluster, my
>> cassandra.yaml looks like so
>>
>> cluster_name: 'node'
>> initial_token: 0
>> num_tokens: 256
>> seed_provider:
>> - class_name: org.apache.cassandra.locator.SimpleSeedProvider
>> parameters:
>> - seeds: "192.168.1.32"
>> listen_address: 192.168.1.32
>> rpc_address: 0.0.0.0
>> endpoint_snitch: RackInferringSnitch
>>
>> Similarly cassandra.yaml for second node
>>
>> cluster_name: 'node'
>> initial_token: 2305843009213693952
>> num_tokens: 256
>> seed_provider:
>> - class_name: org.apache.cassandra.locator.SimpleSeedProvider
>> parameters:
>> - seeds: "192.168.1.32"
>> listen_address: 192.168.1.36
>> rpc_address: 0.0.0.0
>> endpoint_snitch: RackInferringSnitch
>>
>> and so on. . .
>>
>> While trying to start the Server running on the Seed node(192.168.1.32)
>> it throws this nasty exception and didn't start,
>>
>>
>> -bash-4.1$ sudo bin/cassandra
>>
>> -bash-4.1$  INFO 12:19:46,653 Logging initialized
>>  INFO 12:19:46,688 Loading settings from
>> file:/home/cluster/cassandra/conf/cassandra.yaml
>> ERROR 12:19:46,985 Fatal configuration error
>> org.apache.cassandra.exceptions.ConfigurationException: Invalid yaml
>>  at
>> org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:100)
>> at
>> org.apache.cassandra.config.DatabaseDescriptor.loadConfig(DatabaseDescriptor.java:135)
>>  at
>> org.apache.cassandra.config.DatabaseDescriptor.(DatabaseDescriptor.java:111)
>> at
>> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:156)
>>  at
>> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:496)
>> at
>> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:585)
>> Caused by: Can't construct a java object for 
>> tag:yaml.org,2002:org.apache.cassandra.config.Config;
>> exception=Cannot create property=seed_provider for
>> JavaBean=org.apache.cassandra.config.Config@676c6370;
>> java.lang.reflect.InvocationTargetException
>>  in 'reader', line 1, column 1:
>> cluster_name: 'pcross'
>> ^
>>
>> at
>> org.yaml.snakeyaml.constructor.Constructor$ConstructYamlObject.construct(Constructor.java:333)
>>  at
>> org.yaml.snakeyaml.constructor.BaseConstructor.constructObject(BaseConstructor.java:182)
>> at
>> org.yaml.snakeyaml.constructor.BaseConstructor.constructDocument(BaseConstructor.java:141)
>>  at
>> org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:127)
>> at org.yaml.snakeyaml.Yaml.loadFromReader(Yaml.java:481)
>>  at org.yaml.snakeyaml.Yaml.loadAs(Yaml.java:475)
>> at
>> org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:93)
>>  ... 5 more
>> Caused by: org.yaml.snakeyaml.error.YAMLException: Cannot create
>> property=seed_provider for
>> JavaBean=org.apache.cassandra.config.Config@676c6370;
>> java.lang.reflect.InvocationTargetException
>>  at
>> org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.constructJavaBean2ndStep(Constructor.java:299)
>> at
>> org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.construct(Constructor.java:189)
>>  at
>> org.yaml.snakeyaml.constructor.Constructor$ConstructYamlObject.construct(Constructor.java:331)
>> ... 11 more
>> Caused by: org.yaml.snakeyaml.error.YAMLException:
>> java.lang.reflect.InvocationTargetException
>> at
>> org.yaml.snakeyaml.constructor.Constructor$ConstructSequence.construct(Constru

Re: Installing Cassandra Multinode on CentOs coming up with exception

[Mark Reddy]

It is telling you that your yaml is invalid, from looking at the snippet
you have provided it looks like the seed_provider.parameters is not
correctly indented, it should look something like:

seed_provider:
  - class_name: org.apache.cassandra.locator.SimpleSeedProvider
parameters:
 - seeds: "192.168.1.32"


Regards,
Mark


On 26 August 2014 08:12, Vineet Mishra  wrote:

>
> Hi All,
>
> I am installing Cassandra Multinode Setup on a 4 node CentOs Cluster, my
> cassandra.yaml looks like so
>
> cluster_name: 'node'
> initial_token: 0
> num_tokens: 256
> seed_provider:
> - class_name: org.apache.cassandra.locator.SimpleSeedProvider
> parameters:
> - seeds: "192.168.1.32"
> listen_address: 192.168.1.32
> rpc_address: 0.0.0.0
> endpoint_snitch: RackInferringSnitch
>
> Similarly cassandra.yaml for second node
>
> cluster_name: 'node'
> initial_token: 2305843009213693952
> num_tokens: 256
> seed_provider:
> - class_name: org.apache.cassandra.locator.SimpleSeedProvider
> parameters:
> - seeds: "192.168.1.32"
> listen_address: 192.168.1.36
> rpc_address: 0.0.0.0
> endpoint_snitch: RackInferringSnitch
>
> and so on. . .
>
> While trying to start the Server running on the Seed node(192.168.1.32) it
> throws this nasty exception and didn't start,
>
>
> -bash-4.1$ sudo bin/cassandra
>
> -bash-4.1$  INFO 12:19:46,653 Logging initialized
>  INFO 12:19:46,688 Loading settings from
> file:/home/cluster/cassandra/conf/cassandra.yaml
> ERROR 12:19:46,985 Fatal configuration error
> org.apache.cassandra.exceptions.ConfigurationException: Invalid yaml
>  at
> org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:100)
> at
> org.apache.cassandra.config.DatabaseDescriptor.loadConfig(DatabaseDescriptor.java:135)
>  at
> org.apache.cassandra.config.DatabaseDescriptor.(DatabaseDescriptor.java:111)
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:156)
>  at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:496)
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:585)
> Caused by: Can't construct a java object for 
> tag:yaml.org,2002:org.apache.cassandra.config.Config;
> exception=Cannot create property=seed_provider for
> JavaBean=org.apache.cassandra.config.Config@676c6370;
> java.lang.reflect.InvocationTargetException
>  in 'reader', line 1, column 1:
> cluster_name: 'pcross'
> ^
>
> at
> org.yaml.snakeyaml.constructor.Constructor$ConstructYamlObject.construct(Constructor.java:333)
>  at
> org.yaml.snakeyaml.constructor.BaseConstructor.constructObject(BaseConstructor.java:182)
> at
> org.yaml.snakeyaml.constructor.BaseConstructor.constructDocument(BaseConstructor.java:141)
>  at
> org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:127)
> at org.yaml.snakeyaml.Yaml.loadFromReader(Yaml.java:481)
>  at org.yaml.snakeyaml.Yaml.loadAs(Yaml.java:475)
> at
> org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:93)
>  ... 5 more
> Caused by: org.yaml.snakeyaml.error.YAMLException: Cannot create
> property=seed_provider for
> JavaBean=org.apache.cassandra.config.Config@676c6370;
> java.lang.reflect.InvocationTargetException
>  at
> org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.constructJavaBean2ndStep(Constructor.java:299)
> at
> org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.construct(Constructor.java:189)
>  at
> org.yaml.snakeyaml.constructor.Constructor$ConstructYamlObject.construct(Constructor.java:331)
> ... 11 more
> Caused by: org.yaml.snakeyaml.error.YAMLException:
> java.lang.reflect.InvocationTargetException
> at
> org.yaml.snakeyaml.constructor.Constructor$ConstructSequence.construct(Constructor.java:542)
>  at
> org.yaml.snakeyaml.constructor.BaseConstructor.constructObject(BaseConstructor.java:182)
> at
> org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.constructJavaBean2ndStep(Constructor.java:296)
>  ... 13 more
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>  at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>  at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at
> org.yaml.snakeyaml.constructor.Constructor$ConstructSequence.construct(Constructor.java:540)
>  ... 15 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.cassandra.config.SeedProviderDef.(SeedProviderDef.java:33)
>  ... 20 more
> Invalid yaml
>
>
> I am not sure exactly whats making it to throw NullPointer and halt the
> process.
>
> Expert Advice would be appreciated!
> URGENT!
>
> Thanks!
>

Re: installing cassandra on ec2 boxes

[Sameer Farooqui]

Not yet, but I'm working on deploying 0.8.0 beta 2 on multi-regions using a
VPN on Ubuntu. I can share my technique on this mailing list in a little bit
for how I did it.



On Tue, May 10, 2011 at 12:56 PM, Anurag Gujral wrote:

> Are you using different regions in ec2
> Thanks
> Anurag
>
>
> On Tue, May 10, 2011 at 11:19 AM, Sameer Farooqui  > wrote:
>
>> Hi Anurag,
>>
>> We're using an elastic IP for the seed address (public DNS name should
>> also work) and using the private IP (10.255.x.x) for the listen address.
>>
>> As you're getting started, you may also find this blog that my team put
>> together helpful:
>>
>> https://sites.google.com/a/techlabs.accenture.com/cassandra/
>>
>>
>> - Sameer
>>
>>
>>
>> On Tue, May 10, 2011 at 9:39 AM, Anurag Gujral 
>> wrote:
>>
>>> Hi All,
>>>  I am trying to install cassandra on ec2 boxes . I am using
>>> domain names to specify the listen_address and seeds.
>>> I am getting following error from cassandra when I try to create
>>> keyspace.
>>>
>>>  Warning: unreachable nodes IP(address of the cassandra instance)..
>>> schemas agree across the cluste... schemas agree across the cluster
>>>
>>> but when I do telnet IP address 9160 and telnet IPaddress 7000 it works
>>> fine.
>>>
>>> Please help.
>>>
>>> Thanks
>>> Anurag
>>>
>>>
>>>
>>>
>>
>

Re: installing cassandra on ec2 boxes

[Anurag Gujral]

Are you using different regions in ec2
Thanks
Anurag

On Tue, May 10, 2011 at 11:19 AM, Sameer Farooqui
wrote:

> Hi Anurag,
>
> We're using an elastic IP for the seed address (public DNS name should also
> work) and using the private IP (10.255.x.x) for the listen address.
>
> As you're getting started, you may also find this blog that my team put
> together helpful:
>
> https://sites.google.com/a/techlabs.accenture.com/cassandra/
>
>
> - Sameer
>
>
>
> On Tue, May 10, 2011 at 9:39 AM, Anurag Gujral wrote:
>
>> Hi All,
>>  I am trying to install cassandra on ec2 boxes . I am using domain
>> names to specify the listen_address and seeds.
>> I am getting following error from cassandra when I try to create keyspace.
>>
>>  Warning: unreachable nodes IP(address of the cassandra instance)..
>> schemas agree across the cluste... schemas agree across the cluster
>>
>> but when I do telnet IP address 9160 and telnet IPaddress 7000 it works
>> fine.
>>
>> Please help.
>>
>> Thanks
>> Anurag
>>
>>
>>
>>
>

Re: installing cassandra on ec2 boxes

[Sameer Farooqui]

Hi Anurag,

We're using an elastic IP for the seed address (public DNS name should also
work) and using the private IP (10.255.x.x) for the listen address.

As you're getting started, you may also find this blog that my team put
together helpful:

https://sites.google.com/a/techlabs.accenture.com/cassandra/


- Sameer



On Tue, May 10, 2011 at 9:39 AM, Anurag Gujral wrote:

> Hi All,
>  I am trying to install cassandra on ec2 boxes . I am using domain
> names to specify the listen_address and seeds.
> I am getting following error from cassandra when I try to create keyspace.
>
>  Warning: unreachable nodes IP(address of the cassandra instance).. schemas
> agree across the cluste... schemas agree across the cluster
>
> but when I do telnet IP address 9160 and telnet IPaddress 7000 it works
> fine.
>
> Please help.
>
> Thanks
> Anurag
>
>
>
>

Re: Installing Cassandra on windows

[Nick Santini]

glad that helped, about the other issue i wont be able to assist you, im
using cassandra on C# with thrift directly, might be some missconfiguration
in your client


Nicolas Santini



On Fri, Dec 17, 2010 at 6:09 PM, Rajkumar Gupta wrote:

> Thanks a ton Nicolas! This helped..its working now :)
>
> Can you also tell me where to keep the cassandra folder with phpcassa to
> use it with wamp server.. Thanks for your great help!!
>
> Regards
> Rajkumar
>
>
> On Fri, Dec 17, 2010 at 2:31 AM, Nick Santini wrote:
>
>> just tried my self
>> seems to be that you are not starting the cassandra process first
>> the cli is only to access it, not to start it
>>
>> execute cassandra first
>>
>> Nicolas Santini
>>
>>
>> On Fri, Dec 17, 2010 at 9:55 AM, Rajkumar Gupta 
>> wrote:
>>
>>> yes I tried to connect through:
>>>
>>> *cassandra-cli -host localhost -9160*
>>>
>>> It gave me the error *java.net.connection exception: Connection refused*
>>>
>>> but still says: "Welcome to Cassandra CLI". When I try to see the name of
>>> cluster by show, it says not connected to a cassandra instance
>>>
>>>
>>>
>>>
>>>
>>> On Fri, Dec 17, 2010 at 2:12 AM, Nick Bailey  wrote:
>>>
 You are trying to connect through cassandra-cli?

 Does the cassandra log indicate it started correctly? Can you hit port
 9160 (telnet localhost 9160)?


 On Thu, Dec 16, 2010 at 2:34 PM, Rajkumar Gupta >>> > wrote:

>
> Hi there,
>
> I am trying to install Cassandra on windows.. I have downloaded the
> files and when I try to connect to the cassandra through command prompt I
> get an error:
>
>  *java.net connection exception: Connection refused
>
> *I have set the environment variables properly & pointed to my JDK
> installation.
>
> --
>
> ___
>
> Rajkumar Gupta
> Dihing 173,
> Indian Institute of Technology Guwahati
> India
>


>>>
>>>
>>> --
>>>
>>> _
>>>
>>
>>
>
>
> --
>
>

Re: Installing Cassandra on windows

[Rajkumar Gupta]

Thanks a ton Nicolas! This helped..its working now :)

Can you also tell me where to keep the cassandra folder with phpcassa to use
it with wamp server.. Thanks for your great help!!

Regards
Rajkumar

On Fri, Dec 17, 2010 at 2:31 AM, Nick Santini wrote:

> just tried my self
> seems to be that you are not starting the cassandra process first
> the cli is only to access it, not to start it
>
> execute cassandra first
>
> Nicolas Santini
>
>
> On Fri, Dec 17, 2010 at 9:55 AM, Rajkumar Gupta wrote:
>
>> yes I tried to connect through:
>>
>> *cassandra-cli -host localhost -9160*
>>
>> It gave me the error *java.net.connection exception: Connection refused*
>>
>> but still says: "Welcome to Cassandra CLI". When I try to see the name of
>> cluster by show, it says not connected to a cassandra instance
>>
>>
>>
>>
>>
>> On Fri, Dec 17, 2010 at 2:12 AM, Nick Bailey  wrote:
>>
>>> You are trying to connect through cassandra-cli?
>>>
>>> Does the cassandra log indicate it started correctly? Can you hit port
>>> 9160 (telnet localhost 9160)?
>>>
>>>
>>> On Thu, Dec 16, 2010 at 2:34 PM, Rajkumar Gupta 
>>> wrote:
>>>

 Hi there,

 I am trying to install Cassandra on windows.. I have downloaded the
 files and when I try to connect to the cassandra through command prompt I
 get an error:

  *java.net connection exception: Connection refused

 *I have set the environment variables properly & pointed to my JDK
 installation.

 --

 ___

 Rajkumar Gupta
 Dihing 173,
 Indian Institute of Technology Guwahati
 India

>>>
>>>
>>
>>
>> --
>>
>> _
>>
>
>


--

Re: Installing Cassandra on windows

[Nick Santini]

just tried my self
seems to be that you are not starting the cassandra process first
the cli is only to access it, not to start it

execute cassandra first

Nicolas Santini


On Fri, Dec 17, 2010 at 9:55 AM, Rajkumar Gupta wrote:

> yes I tried to connect through:
>
> *cassandra-cli -host localhost -9160*
>
> It gave me the error *java.net.connection exception: Connection refused*
>
> but still says: "Welcome to Cassandra CLI". When I try to see the name of
> cluster by show, it says not connected to a cassandra instance
>
>
>
>
>
> On Fri, Dec 17, 2010 at 2:12 AM, Nick Bailey  wrote:
>
>> You are trying to connect through cassandra-cli?
>>
>> Does the cassandra log indicate it started correctly? Can you hit port
>> 9160 (telnet localhost 9160)?
>>
>>
>> On Thu, Dec 16, 2010 at 2:34 PM, Rajkumar Gupta 
>> wrote:
>>
>>>
>>> Hi there,
>>>
>>> I am trying to install Cassandra on windows.. I have downloaded the files
>>> and when I try to connect to the cassandra through command prompt I get an
>>> error:
>>>
>>>  *java.net connection exception: Connection refused
>>>
>>> *I have set the environment variables properly & pointed to my JDK
>>> installation.
>>>
>>> --
>>>
>>> ___
>>>
>>> Rajkumar Gupta
>>> Dihing 173,
>>> Indian Institute of Technology Guwahati
>>> India
>>>
>>
>>
>
>
> --
>
> ___
>
> Rajkumar Gupta
> Dihing 173,
> Indian Institute of Technology Guwahati
> India
>
> rajku...@iitg.ac.in
> skype: rajkumargupta.iit
>
> http://in.linkedin.com/in/rajkumargupta1
>

Re: Installing Cassandra on windows

[Rajkumar Gupta]

yes I tried to connect through:

*cassandra-cli -host localhost -9160*

It gave me the error *java.net.connection exception: Connection refused*

but still says: "Welcome to Cassandra CLI". When I try to see the name of
cluster by show, it says not connected to a cassandra instance




On Fri, Dec 17, 2010 at 2:12 AM, Nick Bailey  wrote:

> You are trying to connect through cassandra-cli?
>
> Does the cassandra log indicate it started correctly? Can you hit port 9160
> (telnet localhost 9160)?
>
>
> On Thu, Dec 16, 2010 at 2:34 PM, Rajkumar Gupta wrote:
>
>>
>> Hi there,
>>
>> I am trying to install Cassandra on windows.. I have downloaded the files
>> and when I try to connect to the cassandra through command prompt I get an
>> error:
>>
>>  *java.net connection exception: Connection refused
>>
>> *I have set the environment variables properly & pointed to my JDK
>> installation.
>>
>> --
>>
>> ___
>>
>> Rajkumar Gupta
>> Dihing 173,
>> Indian Institute of Technology Guwahati
>> India
>>
>
>


-- 

___

Rajkumar Gupta
Dihing 173,
Indian Institute of Technology Guwahati
India

rajku...@iitg.ac.in
skype: rajkumargupta.iit

http://in.linkedin.com/in/rajkumargupta1

Re: Installing Cassandra on windows

[Nick Bailey]

You are trying to connect through cassandra-cli?

Does the cassandra log indicate it started correctly? Can you hit port 9160
(telnet localhost 9160)?

On Thu, Dec 16, 2010 at 2:34 PM, Rajkumar Gupta wrote:

>
> Hi there,
>
> I am trying to install Cassandra on windows.. I have downloaded the files
> and when I try to connect to the cassandra through command prompt I get an
> error:
>
>  *java.net connection exception: Connection refused
>
> *I have set the environment variables properly & pointed to my JDK
> installation.
>
> --
>
> ___
>
> Rajkumar Gupta
> Dihing 173,
> Indian Institute of Technology Guwahati
> India
>