# MaxRetry Exceptions on Azure **URL:** \ **Category:** Elasticsearch\ **Created:** [August 31, 2015, 7:41am UTC](https://discuss.elastic.co/t/maxretry-exceptions-on-azure/28333 "2015-08-31T07:41:13Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Bart1](https://avatars.discourse-cdn.com/v4/letter/b/439d5e/32.png) [@Bart1](https://discuss.elastic.co/u/Bart1)\ **Post date:** [August 31, 2015, 7:41am UTC](https://discuss.elastic.co/t/maxretry-exceptions-on-azure/28333/1 "2015-08-31T07:41:13Z")
Hi, We are using an ES cluster on (classic) Azure VMs. This cluster is called from an webapplication and a webjob. All seems to work fine, however after several days, we notice that we are getting MaxRetry exceptions. Only by making sure the app and job move to a different (physical machine) the MaxRetry exceptions are gone. After a certain periode the same problem occures again. Does anyone have the same problem? See this link (azure forum) for more detailed information. [https://social.msdn.microsoft.com/Forums/azure/en-US/fe6667eb-f90e-412e-8fee-c2ea2a5aba17/maxretry-exception-from-azure-web-applicaiton-to-elasticsearch-cluster?forum=windowsazurewebsitespreview](https://social.msdn.microsoft.com/Forums/azure/en-US/fe6667eb-f90e-412e-8fee-c2ea2a5aba17/maxretry-exception-from-azure-web-applicaiton-to-elasticsearch-cluster?forum=windowsazurewebsitespreview) Thanks and best regards, Bart ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [September 1, 2015, 7:59am UTC](https://discuss.elastic.co/t/maxretry-exceptions-on-azure/28333/2 "2015-09-01T07:59:42Z")
What is in your ES logs? ---
**Author:** ![Bart1](https://avatars.discourse-cdn.com/v4/letter/b/439d5e/32.png) [@Bart1](https://discuss.elastic.co/u/Bart1)\ **Post date:** [September 1, 2015, 8:20am UTC](https://discuss.elastic.co/t/maxretry-exceptions-on-azure/28333/3 "2015-09-01T08:20:40Z")
> [@Bart1](#): > > We are using an ES cluster on (classic) Azure VMs. This cluster is called from an webapplication and a webjob. All seems to work fine, however after several days, we notice that we are getting MaxRetry exceptions. Only by making sure the app and job move to a different (physical machine) the MaxRetry exceptions are gone. After a certain periode the same problem occures again. > > Does anyone have the same problem? Hi Mark, we did find anything that could point us to the rootcause. The cluster was running fine and not under pressure. When it happens again I will make sure all logs (client side and on the cluster) are gathered. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [September 1, 2015, 8:22am UTC](https://discuss.elastic.co/t/maxretry-exceptions-on-azure/28333/4 "2015-09-01T08:22:45Z")
It sounds like an Azure specific problem, but I don't know enough about the platform myself. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [September 1, 2015, 8:41am UTC](https://discuss.elastic.co/t/maxretry-exceptions-on-azure/28333/5 "2015-09-01T08:41:08Z")
Are you using azure discovery plugin? ---
**Author:** ![Bart1](https://avatars.discourse-cdn.com/v4/letter/b/439d5e/32.png) [@Bart1](https://discuss.elastic.co/u/Bart1)\ **Post date:** [September 23, 2015, 6:29am UTC](https://discuss.elastic.co/t/maxretry-exceptions-on-azure/28333/6 "2015-09-23T06:29:26Z")
Hi David, since we rebuild the cluster in Azure from scratch, the problem hasn't occurred anymore (since three weeks). Best regards, Bart ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:48pm UTC](https://discuss.elastic.co/t/maxretry-exceptions-on-azure/28333/7 "2017-07-05T23:48:34Z")