Search results

How are you presenting the disk to your server is it via a Raid Card?

What is the latency like? You was able to run a large amount of omping without a drop? Can every node ping another / corosync hostname e.t.c

Is the roadmap fairly up to date or is there any other key/big features planned for 5.0?

Fully understand about maintenance, and yes if I am doing anything more than a "apt-get dist-upgrade" then I would remove all VM's, but when applying updates that have no requirement for a reboot of the node so can be done live, if their is an update for the corosync package, this obviously...

I understood this was still a VM moving to another node, but this will also stop a node from powering off if corosync does not respond? I know they may sound the same just wanted to make sure!

Will leave this down to the dev's, may be a bug or just a one off. Main thing is as you have proven your storage is still there and useable, to me does not look a CEPH issue otherwise you would not be able to create a new disk and make use of this.

Can you paste the contents of your VM's config file? located @ /etc/pve/qemu-server

What does "rbd ls pool2" show via terminal

Recently been trying out HA in Proxmox, just run an apt-get dist-upgrade on one node, this had an update for corosync causing the node to be fenced (rebooted). 1/ I have done some searching on the forum and have found a reply stating to stop two services on the node in question before updating...

Sure agree with you there was just confirming.

Maybe I understand wrong, but I/O won't stop if osd_backfill_full_ratio is reached, only recovery will stop. I/O will only stop @ mon osd_full_ratio, which are two different values (backfill by default lower than osd_full_ratio to stop a backfill making OSD go full and cause write's to be blocked.

CEPH has built in limits per OSD/PG/POOL, this will cause any rebalance to be suspended once this limit is hit, once new storage is added then it will continue to rebalance belongs the % is lower than the threshold. However this does mean during this time you run the risk of a further failure...

A) It could help depends how good the RAID1 disks are B) No belongs they are setup correctly C) Size of 3 you can expect slightly worse performance over 2. The rados benchmark is what id expected as your hitting around 50% of the drives write performance.

What are you confused about we both said the same thing.

Depending on the value you changed your need to restart that service for it to pickup the new value, however you can inject the vars live into the running services using : http://www.sebastien-han.fr/blog/2012/10/22/ceph-inject-configuration-without-restart/

It is documented in many online places including : http://ceph-users.ceph.narkive.com/px2L2fHc/is-it-still-unsafe-to-map-a-rbd-device-on-an-osd-server I have yet to see a clear place that a particular kernel version has the issue 100% fixed, and is not something I wish to test myself. KRBD vs...

1/ I would set your PG Number to 2048 (this shouldn't effect performance too much but is a better value than 1050 you have set) 2/ What tests are you doing to check performance and what results are you getting? As your collocating the Journal on the same disks you will only get a max of 1/2...

apt-get update && apt-get dist-upgrade

apt-get update; apt-get dist-upgrade; I would hold off the autoremove until you have checked everything is working correctly.

Using the hardware you have: Each server: 2* SM863 4 * MX300 SM863 on each create: 1 Partition for Proxmox (Equal Size) 80GB 2 * Journal Partition (4 * 10GB) ZFS the two first partitions from each SM863 during the Proxmox Installer, use the remaining 4 Journal partitions for each MX300 OSD...