----- Original Message ----- > From: "Saggi Mizrahi" <smizr...@redhat.com> > To: "Francesco Romani" <from...@redhat.com> > Cc: "vdsm-devel" <vdsm-devel@lists.fedorahosted.org>, "Yaniv Bronheim" > <ybron...@redhat.com> > Sent: Tuesday, March 25, 2014 1:45:22 PM > Subject: Re: thread pool implementation > > The thing that worries me the most is stuck threads. > I hate them! > > Could we move to multiple libvirt connections scheme? > Where if a call takes too long we just close the connection. > I know that the call is still running in libvirt but then it's > their problem and not my problem. That way the thread pool > doesn't need to handle this use case making it much simpler. > > Because apart from the problem of libvirt calls getting stuck > we just need a run of the mill threadpool solution.
It is an interesting point. I'll investigate the multiple libvirt connection Idea. Bests, -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani _______________________________________________ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
