Search results

I'm using IPoIB and not Ethernet, and all of my hardware is kind of a mixed bag of Ebay specials. The system's boot disks are actually shucked PNY 128GB SSDs that I mounted to a custom 3D printed bracket and ziptied to the back of the case because I didn't want to use one of the 3 drive bays...

Ouch, that balance time... I would be very interested to know how it goes for you once it is complete. I set my cluster up over a year and a half ago and just kind of took for granted at the time that my performance was super bad because of the wonky hardware. Now that I've finally gotten...

I can't claim any expertise there, but my understanding was that any "slow_*" values would indicate that something is bottlenecking. In this case it was related to not having enough space for the DB/WAL data which should be about 4% the size of the storage drives from what I have been reading...

Actually, after banging my head into the keyboard for a few days I think I might have finally gotten a lead on my issue. I have 3 active nodes at the moment with two drives 1TB/16TB drives each. (I know this is sub optimal and it's really not helping, but I don't think it's my real issue.) Each...

So from my testing it does appear that the commands I mentioned above work. This should allow you to set these values on a per node basis. As for performance changes, @realguob, @alexskysilk, what kind of performance changes did you see if any? I am pretty sure I identified other serious issues...

I hate to necro a thread like this, but I also am curious what happened for everyone here. When I set up my current cluster I thought I'd try out CEPH, and I've been impressed by a lot of it's ability. The performance on the other hand is downright abysmal and I'm struggling to determine why...

Okay, so... If I'm understanding this correctly it is possible to do this, though you can't do it in the config file. It looks like CEPH is shifting away from a config file to a configuration database. This appears to be the only way you can do it...

I wasn't sure on this at first either. From @realguob's original note though it looks like they need to be un-linked so they can be edited individually. Right now I'm looking to see if there is a way I can specify the GUIDs for each node without needing to unlink them. I'll update if I find...

I haven't had a lot of time to mess with this, but my situation is that I have 4 identical servers and one that is running different physical hardware, but is otherwise configured identical that are all working with the exception of this one node. I've dug through the logs for a few hours now...

I have been having exactly the same issue on one of my servers for a bit now. Just had the time to figure out what was causing it. Did you ever end up getting this resolved? The other thread I found talking about this just ended how many of them seem to, descending into numerous requests for...

I spent like 10 minutes trying to figure out why this didn't work before realizing I had a typo and put "rdb" instead of "rbd." I feel dumb. lol Thank you for posting this. Super helpful.

I have been having a consistent and incredibly frustrating issue where a single node in my datacenter being rebooted causes the entire datacenter to fail and the web GUI to malfunction and become useless. I then need to log into the node(s) over SSH and either restart cluster related services...

How would I have changed this? I suppose it's possible but I would have had to manually edit the renewal script for the built in automated ACME GUI. I didn't do anything (this time) that wasn't a GUI option. ACME didn't originally mess up the pve-ssl.pem file. It got messed up on automatic...

So unfortunately I need to open this again as the issue came back up and I think this is a problem with Proxmox's ACME script. As I stated in my last post I configured the custom cert and everything worked just fine. A few days ago however Spice stopped working again. Just as last time I went...

It seems like that is the answer. Wow now I feel kind of dumb. I updated my VM to Debian 10 and the issue is completely gone. Proxmox still throws errors if I remove the CPU, cpuunits or cpulimit fields but other than that the issue is gone. Memory hotunplug is working flawlessly now too...

I'm not getting any errors in the syslog and the console froze just like the desktop. When I do what you described the VM will start with 1 vCPU and I can add them, but I still can't removed them. The VM will hang if I try to remove a CPU at any point after this. I tested this on a second...

Not sure exactly what you mean by that. I followed what you said and the VM froze after I got the error. When I stopped it and started it again the VM only had 1 vCPU like I had told it to set itself to. This is basically the same as shutting the VM down and adding or removing cores though...

It was my understanding that hot-unplug worked which is why it surprised me when it didn't. As for kernel messages, I just checked and there are no messages as far as I can tell. The entire OS seems to hang the moment the memory or CPU are unplugged so I'm not surprised. As for the code, I'm...