Description of problem: Here is my volume configuration: # gluster volume info testvol Volume Name: testvol Type: Distribute Status: Started Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: server1:/bricks/0001 Options Reconfigured: performance.io-thread-count: 1 performance.flush-behind: off performance.quick-read: off Now, when I am doing file operations, I can see two glusterfsd threads are writing to the brick. First I found out this using `top -p $(pgrep glusterfsd) -H`, there it was clear that two thread were consuming CPU. Then I performed strace on those threads. I could see both of these threads were doing IO. Version-Release number of selected component (if applicable): glusterfs 3.2.6 built on May 16 2012 13:20:35 Repository revision: git://git.gluster.com/glusterfs.git Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com> GlusterFS comes with ABSOLUTELY NO WARRANTY. You may redistribute copies of GlusterFS under the terms of the GNU General Public License. How reproducible: Steps to Reproduce: 1. Create the above volume configuration. 2. Mount that volume and do IO. Actual results: Expected results: Additional info: I have attached
Created attachment 587374 [details] glusterfsdump created using kill -USR1
Hey Sorry. I guess I am mixing it up. One thread is doing I guess the network i/o and the other process is actually handling disk/io. If this is the case, this bug is invalid. Let me confirm once.
when you say 'io-thread-count 1', that means one extra thread will be created other than the main thread which is polling on network.