Description of problem: CPU spike on any node causing files/volume unavailable Version-Release number of selected component (if applicable): We have 3 node gluster, out of which we are using node 3 as arbiter Node1 and Node2 version: 4.1.5 Node3 version:4.1.7 How reproducible: Production envirnoment, so we need to wait until the issue occurs Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Could you provide some more details? 1. gluster volume info 2. what is the access mechanism (fuse?) and its gluster version 3. On which node is the CPU spike observed? 4. By files being unavailable, do you mean the file is missing when you try to access from the client or is it that the client appears to be hung? 5. Were there any self-heals going on at the time of the spike? 6. The next time this occurs, please capture the a) volume profile info and b)`top -H <pid of the process that consumes cpu (I'm guessing it is the brick)`. You cab attach the results to this bug. Note: It is advisable to have all servers and clients at the same gluster version.
(In reply to Ravishankar N from comment #1) > b)`top -H <pid of the process that consumes cpu (I'm guessing it is the > brick)`. Sorry made a typo, this is just `top -H`
Hi, I'm closing this bug since I haven't heard from you. Please feel free to re-open with the information I requested/ steps to reproduce.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days