On Thu, May 4, 2017 at 11:18 PM, Nicholas A. Bellinger <nab@xxxxxxxxxxxxxxx> wrote: >> > One thing that comes to mind is the per target endpoint (eg: TPG >> > attribute in targetcli) is 'default_cmdsn_depth', which by default is >> > set to 64. This controls how many I/Os can be in flight for a single >> > iscsi session. >> > >> > I"m not sure what the default is for tgtd in rhel6, but with enough >> > initiators connected you might want to consider setting this to >> > something like 16, 8, or lower. >> >> I'm pretty sure i tried tweaking that parameter (as it was suggested >> elsewhere on the internet), but it didn't make a difference. But i'll >> recheck my notes and re-run the tests to be sure. > > Yeah, I'd start out really conservative at default_cmdsn_depth=1 and > start working up from there to understand if it's something related to > the number of outstanding I/O that is causing TCP connections to be > constantly be dropped. it looks like setting this to 1 fixed the issue. or at least i don't see timeouts now. i checked back through my notes, i cut the value to 32 and 16, but never all the way down to 1 i'll do some more testing and see if anything pop's up -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
