5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
@EricOBR, In that case, you should also open a case with our support so they can apply the fix we have internally for this. -Said
@EricOBR Hi, I looked at the case 00704574, and searched for the string “java.lang.NullPointerException”, but did not see any reference to that. I also checked provided logs but no files there indicating the same string. You might have provided that but I could not find it there. Is this the same issue we are talking about here? If this is the same exact issue, please report about the string “java.lang.NullPointerException” on the case. I will add my notes there so the support can see it after you let me know about this. If it is not the same exact issue (an upgrade that has already happened without the NCC being in revision 3.9.3 before the upgrade and now you see the string “java.lang.NullPointerException” on prism) , then open another case and do mention it there. The issue you are seeing may be similar but may not be exactly the same issue (just a thought). Let me know how it goes. -Said
@EricOBR Ok, I added a private note for support hoping they can relate the reported issue and your case.. Make sure they have done a WebEx or zoom session with you to observe the issue directly. Let me know how it goes. -Said
@Hendra Yes, you can expand cluster storage by swapping the present smaller size disks with larger ones. You do have to remove the small disk(s) from the cluster first and then introduce the larger capacity disk to the cluster. As for comparing with adding a node, addition of a node will provide you with more CPU and memory in the cluster as opposed to just storage capacity. Also, if you are swapping disk, make sure you do it one disk at a time on one node at a time. By that I mean, you should keep the balance of storage on each node. if you swap “disk one on the first node, and then swap the second disk on the second node and so on, and once you are done with all nodes, you can come back to “node one” and perform the same for the second disks on each node. This way the balance of capcity across node will be kept.
@Hendra I am sure both are valid, but adding a node is more straight forward and contains no restriction with regard to the amount of data you already have in the luster. Swapping disks is time-consuming and there is always a chance that you may not have enough space on the cluster to remove a disk and maintain data resiliency. I hope this helps a bit.
@Eric B It really depends on the type of licensing you already have for your cluster. There are certain license types like “starter”, “pro”, “ultimate” etc, that has to do with different features in your cluster, these do not need any change in licensing if you add disks. But if you have capacity-based licensing, yes it does require. You are best talking to your account team or salesperson to find out about it if you are not sure. Also, check “https://www.nutanix.com/products/software-options”. -Said
@PeWu Good observation. If the numbers are part per million (and it makes sense, but probably need to be investigated to be 100% sure) then a number like 144 is basically %0.0144 (as you mentioned), which means the instruction did not wait in the queue to be executed much at all. The focus of response was the fact that the percentage can be above 100%; which they can cause this is a ratio expressed in ppm (as you pointed).
@markinh yes, these are different plugins
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.