Connecting Cloud Innovators: Building Community at .NEXT 2024
case number 00254576. Low priority, we aren't at risk or anything. mostly, either I am reading the data wrong or planning is calculating wrong (or somwhere in the middle). either way, we aren't seeing any impacting issues at the moment, so take your time.
[url=http://next.nutanix.com/member/profile?mid=8872]harryhy[/url] NCC version is 3.1.0 and Prism Central 5.1.3. So this is probably the same issue.
[url=http://next.nutanix.com/member/profile?mid=8872]harryhy[/url] cool, i'll figure out a time for that and report back in a few days to let you know if it resolved.
Yes, I see dlink7,s reply. Thanks [user=33]dlink7[/user] for the good info on expected performance under ideal situations. That does give me a good baseline. Our issue is definitely latency. Our remote site is across the continental US, and our per VM size is 30TB (10TB used) on a single disk. as you can imagine, this creates a bottleneck for us. Replications with default settings are not meeting RPO. Our AOS version is 5.5.2. I have found (with help from support) these tunable settings within the cluster: [code]nutanix@NTNX:~$ python /home/nutanix/serviceability/bin/edit-aos-gflags | grep stargate_ 2018-06-08 10:00:09 INFO zookeeper_session.py:110 edit-aos-gflags is attempting to connect to Zookeeper stargate_cerebro_replication_max_rpc_vblocks = 16 #default 4 stargate_cerebro_replication_max_rpc_data = 4194304 #default 1048576 stargate_cerebro_max_outstanding_vdisk_replication_rpcs = 16 #default 4 stargate_cerebro_replication_param_multiplier = 32
[user=84063]Bradley4681[/user] When you run: [code]nutanix@NTNX:~$ python /home/nutanix/serviceability/bin/edit-aos-gflags --service=stargate [/code] You enter in to a text editor with all the stargate service glfags. Here, you can edit the settings to achieve different results. The settings i adjusted that wound up working for me basically amounted to an increase in the number of streams per vdisk, the amount of data saturation allowed on the line, and the priority that stargate gave to replication processing. This allowed me to overcome the high latancy on my cross US pipe. You can find my specific setting adjustments in the block that you quoted. Also, you'll probably need to get a genesis restart at a minimum. Its worth noting a few things about my environment that made this combination of settings work without any negative impacts: [list=1] [*][b]Homogeneous images:[/b] every guest in the entire cluster is doing the same type of work, is the same size and has th
Thanks [user=7898]aluciani[/user] ! somehow i think i accidentally marked this as solved, but it is not yet. I appreciate you investigating!
@rhunt when this was checked we were 5.5.3.1. I’ll check on one of our 5.10 and reply back.
@rhunt unfortunately i resolved all of the alerts that included a large number of VMs, so it’s inconclusive. I’ll try to generate a few more :P
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.