- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Aug 25 2022
Move the checksum computation inside the if
Aug 24 2022
Everything is almost ready to start the ingestion tests:
- The deployment of the replayers is implemented
- The monitoring can also be easily deployed in a kubernetes cluster having the prometheus operator installed [1]
- the grafana dashboards are also available as templates [1]
Aug 23 2022
Aug 22 2022
Aug 20 2022
Aug 19 2022
Aug 18 2022
all server reconfigured and cassandra started on them:
/opt/cassandra/bin/nodetool status Datacenter: sesi_rocquencourt ============================= Status=Up/Down |/ State=Normal/Leaving/Joining/Moving -- Address Load Tokens Owns (effective) Host ID Rack UN 192.168.100.184 88.65 KiB 16 34.3% e0c24d24-6f68-4a26-8561-94e67b58211a rack1 UN 192.168.100.181 84.71 KiB 16 31.3% 1d9b9e7d-b376-4afe-8f67-482e8412f21b rack1 UN 192.168.100.186 69.07 KiB 16 34.2% 0dd3426d-9159-47bd-9b4e-065ff0fbb889 rack1 UN 192.168.100.183 69.08 KiB 16 37.1% 78281a92-7fa0-43bd-bc33-c5b419ee8715 rack1 UN 192.168.100.185 69.07 KiB 16 32.2% abf9b69e-3cec-4ac3-a195-a54481e4d9da rack1 UN 192.168.100.182 74.05 KiB 16 30.9% eca5ea5d-8bd5-4301-9a5e-ffa01aa1b7e5 rack1
Recreating the zpool correctly:
# mixedused ls /dev/disk/by-id/nvme-MO003200KXAVU* | grep -v part | xargs -t zpool create -o ashift=12 -O mountpoint=none mixeduse zfs create -o mountpoint=/srv/cassandra/instance1/data mixeduse/cassandra-instance1-data
Testing the performances of the different configuration (on a zfs pool with only one disk):
- disk block: 512k / zpool ashift:9
zpool create -o ashift=9 -O mountpoint=none mixeduse /dev/disk/by-id/nvme-MO003200KXAVU_SJA4N7938I0405A0U zfs create -o mountpoint=/srv/cassandra/instance1/data -o atime=off -o relatime=on mixeduse/cassandra-data cd /srv/cassandra/instance1/data bonnie++ -d . -m cassandra04 -u nobody Using uid:65534, gid:65534. Writing a byte at a time...done Writing intelligently...done Rewriting...done Reading a byte at a time...done Reading intelligently...done start 'em...done...done...done...done...done... Create files in sequential order...done. Stat files in sequential order...done. Delete files in sequential order...done. Create files in random order...done. Stat files in random order...done. Delete files in random order...done. Version 2.00 ------Sequential Output------ --Sequential Input- --Random- -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- Name:Size etc /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP cassandra04 515496M 293k 99 1.0g 99 703m 99 661k 99 1.4g 91 13717 463 Latency 48216us 7316us 8224us 23303us 7928us 1606us Version 2.00 ------Sequential Create------ --------Random Create-------- cassandra04 -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete-- files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP 16 16384 98 +++++ +++ 16384 8 +++++ +++ +++++ +++ 16384 99 Latency 2679us 1207us 4851ms 2850us 138us 301us 1.98,2.00,cassandra04,1,1659338044,515496M,,8192,5,293,99,1080974,99,720299,99,661,99,1488832,91,13717,463,16,,,,,28232,98,+++++,+++,2018,8,+++++,+++,+++++,+++,24821,99,48216us,7316us,8224us,23303us,7928us,1606us,2679us,1207us,4851ms,2850us,138us,301us
The nvme format command didn't succeed on the write intensive disk. It never exits and the disk become unresponsive after that.
Aug 17 2022
use inline_yaml instead of to_yaml
thanks for the hint, I completely forgot about it
Aug 16 2022
- Rebase
- Override the jmx port value via the JVM_EXTRA_OPTS environment
- Inline the cassandra.yaml properties in hiera
Aug 12 2022
Setting -Dcassandra.jmx.local.port / -Dcassandra.jmx.remote.port / -Dcom.sun.management.jmxremote.rmi.port in the $JVM_EXTRA_OPTS env var should override what this file configured
I specified why on the first line of the file, but I realize it not very visible.
The puppet code is ready for review. It was updated to support multi instances deployment in anticipation of T4375.
Aug 11 2022
Aug 10 2022
For the record, the issues related to the commitlog_directory configuration:
After spending some time to successfully start a cassandra cluster of 2 nodes with a declarative configuration), these are the observations:
- A service can't be used to expose the cassandra ports to the clustrer, the pod address must be used. It's because cassandra use the dns name provided as listen address
- It should work by setting the listen address to 0.0.0.0 but it's stongly recommanded to not use this in the documentation
Setting listen_address to 0.0.0.0 is always wrong.
- Using internal pod address will avoid multi DC deployment for the future
Aug 9 2022
Aug 8 2022
VPN certificate revoked in opensense
looks good, thanks.
I'm not sure if it's not better to keep the KAFKA_BROKER_ID closed to the instance declaration as it needs to be unique in a cluster and can't be shared between the instances.
But otherwise, thank, it's simpler like that.