<html><body><div style="font-family: lucida console,sans-serif; font-size: 12pt; color: #000000"><div>Wouldn't the thread count relate to the number of bricks in the volume, rather that peers in the cluster?<br></div><div><br></div><div><br></div><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Kelly Burkhart" <kelly.burkhart@gmail.com><br><b>To: </b>gluster-devel@nongnu.org<br><b>Sent: </b>Friday, 31 January, 2014 9:52:38 AM<br><b>Subject: </b>[Gluster-devel] libgfapi threads<br><div><br></div><div dir="ltr"><div><div><div><div><div><div><div><div><div>Hello, I'm working through using libgfapi and am curious about the number of background threads started. I have a simple cluster with four bricks on four peers. On my client machine I run a program that does this:<br>
<br></div>glfs_new()<br></div>glfs_set_volfile_server()<br></div>glfs_set_logging()<br></div>glfs_init()<br>pause()<br></div>glfs_fini()<br></div>pause()<br><div><br></div></div>At the first pause, right after glfs_init, there are four child threads created. Is it a coincidence that the api creates the same number of threads as cluster peers? I'd hate to think that if I had a thousand peers I'd have a thousand threads.<br>
<br>Second, the threads don't shut down after the call to glfs_fini().<br><div><br></div>Can anyone shed some light on what's going on?<br><div><br></div></div>Thanks,<br><div><br></div></div>-Kelly<br></div>
<br>_______________________________________________<br>Gluster-devel mailing list<br>Gluster-devel@nongnu.org<br>https://lists.nongnu.org/mailman/listinfo/gluster-devel<br></blockquote><div><br></div></div></body></html>