[ovirt-devel] In AIO environment, why engine and vdsm communicate timeout

[Sandro Bonazzola]

On Tue, Mar 1, 2016 at 12:38 PM, 李坚 <lijian at cloud-times.com> wrote:

> Dear ovirt developers,
>
>
>   In ovirt 3.5.x version, there is a problem  communicating timeout
> between ovirt-engine and vdsm in AIO environment. The default timeout is
> 180 seconds, but vdsm returning a request cost 500 seconds. The AIO host is
> light load and do you know why so slowly.
>
>
>   I remember that it don't have this problem in 2.x version. please help
> me, thanks!
>


Hi, please note that AIO is meant for testing and demo purpose, it's
deprecated in 3.5 and 3.6 and won't be available in 4.0.
It's highly recommended to use Self Hosted Engine instead of All In One.



>
>
>   Thanks & Best Regards
>
>
> ----------------------------------------------------------------------------------------------------------------------------
>
>  ovirt deleloper
>
>
>
> _______________________________________________
> Devel mailing list
> Devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>



-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20160307/8a62eb5b/attachment-0001.html>