Azure Batch, Low priority nodes not working at allWhy are my new Azure end points not working?if exist !SOMEPATH! not working in batch fileSQL Azure insert query ten times slower on V12 than V11?Azure-CLI commands not workingAzure VM inbound rules not workingazure port forwarding not workingAzure Load Balancing HTTP probe not workingChanging Azure Backup Retention policy not reducing Azure storage used?Azure ssl certificate not workingDoes an Azure Backup of a VM bump users off the system during execution?

Did 20% of US soldiers in Vietnam use heroin, 95% of whom quit afterwards?

便利な工具 what does な means

Time complexity of an algorithm: Is it important to state the base of the logarithm?

Why did the person in charge of a principality not just declare themself king?

How can I tell if I'm being too picky as a referee?

Is it legal to have an abortion in another state or abroad?

Beginner looking to learn/master musical theory and instrumental ability. Where should I begin?

Can I tell a prospective employee that everyone in the team is leaving?

Why did Drogon spare this character?

Did this character show any indication of wanting to rule before S8E6?

Manager questioning my time estimates for a project

I know that there is a preselected candidate for a position to be filled at my department. What should I do?

Public transport tickets in UK for two weeks

Which European Languages are not Indo-European?

Is this statement about cut time correct?

How to patch glass cuts in a bicycle tire?

Expected maximum number of unpaired socks

Why do Russians almost not use verbs of possession akin to "have"?

USPS Back Room - Trespassing?

The art of clickbait captions

How to deal with a colleague who is being aggressive?

What weight should be given to writers groups critiques?

What's difference between "depends on" and "is blocked by" relations between issues in Jira next-gen board?

Why does this if statement return true



Azure Batch, Low priority nodes not working at all


Why are my new Azure end points not working?if exist !SOMEPATH! not working in batch fileSQL Azure insert query ten times slower on V12 than V11?Azure-CLI commands not workingAzure VM inbound rules not workingazure port forwarding not workingAzure Load Balancing HTTP probe not workingChanging Azure Backup Retention policy not reducing Azure storage used?Azure ssl certificate not workingDoes an Azure Backup of a VM bump users off the system during execution?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








1















We have been using low priority nodes in my company for a really long time. Every now and then we get preempted nodes but our tasks end up running eventually.



We have 1 dedicated node, and we scale up to 20 low priority ones. For the last 3 days no low priority node has been created when scaling. Scaling shows it's trying to set up more nodes but it just stays like that.



Is there any solution for this? Are low priority nodes broken at the moment?










share|improve this question




























    1















    We have been using low priority nodes in my company for a really long time. Every now and then we get preempted nodes but our tasks end up running eventually.



    We have 1 dedicated node, and we scale up to 20 low priority ones. For the last 3 days no low priority node has been created when scaling. Scaling shows it's trying to set up more nodes but it just stays like that.



    Is there any solution for this? Are low priority nodes broken at the moment?










    share|improve this question
























      1












      1








      1








      We have been using low priority nodes in my company for a really long time. Every now and then we get preempted nodes but our tasks end up running eventually.



      We have 1 dedicated node, and we scale up to 20 low priority ones. For the last 3 days no low priority node has been created when scaling. Scaling shows it's trying to set up more nodes but it just stays like that.



      Is there any solution for this? Are low priority nodes broken at the moment?










      share|improve this question














      We have been using low priority nodes in my company for a really long time. Every now and then we get preempted nodes but our tasks end up running eventually.



      We have 1 dedicated node, and we scale up to 20 low priority ones. For the last 3 days no low priority node has been created when scaling. Scaling shows it's trying to set up more nodes but it just stays like that.



      Is there any solution for this? Are low priority nodes broken at the moment?







      azure batch






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked May 10 at 23:49









      Renato FontesRenato Fontes

      63




      63




















          2 Answers
          2






          active

          oldest

          votes


















          1















          Use low-priority VMs with Batch



          The tradeoff for using low-priority VMs is that those VMs may not be
          available to be allocated or may be preempted at any time, depending
          on available capacity.




          Expecting a low priority instance to be available at all is unreasonable. Excess capacity may simply not be there indefinitely.



          First check the status dashboard and/or social media. I don't see reported problems with Batch.



          Shop different instance sizes in different regions. Sometimes the lack of surplus for your favorite size is local.



          Add full price instances for the work that must get done.






          share|improve this answer























          • Low priority nodes tend to be available at some point during the day. They definitely are never unavailable for 3 days in a row. We've been using them for 2 years now. The problem was that some VM objects/resources were deleted, this broke low priority nodes but not dedicated ones.

            – Renato Fontes
            May 13 at 17:12


















          0














          The problem was quite complicated, and probably a bug in Azure Batch.



          Some VM objects had been removed from the resource group by someone in the team. This caused Low Priority VMs to be unable to start, the weird part is that Dedicated VMs actually started correctly.



          I solved it by using the VM image to create a new VM, then a new IMAGE, and recreated the Azure Batch pool using this new image. The important part was not deleting the VM objects.






          share|improve this answer























          • One more thing so you know if you are trying to figure something out in Batch: Batch is buggy. Specially when using linux VMs. Ubuntu 1804 was completely broken for batch at least a few months ago(I'm using 1604).

            – Renato Fontes
            May 13 at 17:14











          Your Answer








          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "2"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f966789%2fazure-batch-low-priority-nodes-not-working-at-all%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          2 Answers
          2






          active

          oldest

          votes








          2 Answers
          2






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1















          Use low-priority VMs with Batch



          The tradeoff for using low-priority VMs is that those VMs may not be
          available to be allocated or may be preempted at any time, depending
          on available capacity.




          Expecting a low priority instance to be available at all is unreasonable. Excess capacity may simply not be there indefinitely.



          First check the status dashboard and/or social media. I don't see reported problems with Batch.



          Shop different instance sizes in different regions. Sometimes the lack of surplus for your favorite size is local.



          Add full price instances for the work that must get done.






          share|improve this answer























          • Low priority nodes tend to be available at some point during the day. They definitely are never unavailable for 3 days in a row. We've been using them for 2 years now. The problem was that some VM objects/resources were deleted, this broke low priority nodes but not dedicated ones.

            – Renato Fontes
            May 13 at 17:12















          1















          Use low-priority VMs with Batch



          The tradeoff for using low-priority VMs is that those VMs may not be
          available to be allocated or may be preempted at any time, depending
          on available capacity.




          Expecting a low priority instance to be available at all is unreasonable. Excess capacity may simply not be there indefinitely.



          First check the status dashboard and/or social media. I don't see reported problems with Batch.



          Shop different instance sizes in different regions. Sometimes the lack of surplus for your favorite size is local.



          Add full price instances for the work that must get done.






          share|improve this answer























          • Low priority nodes tend to be available at some point during the day. They definitely are never unavailable for 3 days in a row. We've been using them for 2 years now. The problem was that some VM objects/resources were deleted, this broke low priority nodes but not dedicated ones.

            – Renato Fontes
            May 13 at 17:12













          1












          1








          1








          Use low-priority VMs with Batch



          The tradeoff for using low-priority VMs is that those VMs may not be
          available to be allocated or may be preempted at any time, depending
          on available capacity.




          Expecting a low priority instance to be available at all is unreasonable. Excess capacity may simply not be there indefinitely.



          First check the status dashboard and/or social media. I don't see reported problems with Batch.



          Shop different instance sizes in different regions. Sometimes the lack of surplus for your favorite size is local.



          Add full price instances for the work that must get done.






          share|improve this answer














          Use low-priority VMs with Batch



          The tradeoff for using low-priority VMs is that those VMs may not be
          available to be allocated or may be preempted at any time, depending
          on available capacity.




          Expecting a low priority instance to be available at all is unreasonable. Excess capacity may simply not be there indefinitely.



          First check the status dashboard and/or social media. I don't see reported problems with Batch.



          Shop different instance sizes in different regions. Sometimes the lack of surplus for your favorite size is local.



          Add full price instances for the work that must get done.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered May 11 at 13:53









          John MahowaldJohn Mahowald

          10.2k1714




          10.2k1714












          • Low priority nodes tend to be available at some point during the day. They definitely are never unavailable for 3 days in a row. We've been using them for 2 years now. The problem was that some VM objects/resources were deleted, this broke low priority nodes but not dedicated ones.

            – Renato Fontes
            May 13 at 17:12

















          • Low priority nodes tend to be available at some point during the day. They definitely are never unavailable for 3 days in a row. We've been using them for 2 years now. The problem was that some VM objects/resources were deleted, this broke low priority nodes but not dedicated ones.

            – Renato Fontes
            May 13 at 17:12
















          Low priority nodes tend to be available at some point during the day. They definitely are never unavailable for 3 days in a row. We've been using them for 2 years now. The problem was that some VM objects/resources were deleted, this broke low priority nodes but not dedicated ones.

          – Renato Fontes
          May 13 at 17:12





          Low priority nodes tend to be available at some point during the day. They definitely are never unavailable for 3 days in a row. We've been using them for 2 years now. The problem was that some VM objects/resources were deleted, this broke low priority nodes but not dedicated ones.

          – Renato Fontes
          May 13 at 17:12













          0














          The problem was quite complicated, and probably a bug in Azure Batch.



          Some VM objects had been removed from the resource group by someone in the team. This caused Low Priority VMs to be unable to start, the weird part is that Dedicated VMs actually started correctly.



          I solved it by using the VM image to create a new VM, then a new IMAGE, and recreated the Azure Batch pool using this new image. The important part was not deleting the VM objects.






          share|improve this answer























          • One more thing so you know if you are trying to figure something out in Batch: Batch is buggy. Specially when using linux VMs. Ubuntu 1804 was completely broken for batch at least a few months ago(I'm using 1604).

            – Renato Fontes
            May 13 at 17:14















          0














          The problem was quite complicated, and probably a bug in Azure Batch.



          Some VM objects had been removed from the resource group by someone in the team. This caused Low Priority VMs to be unable to start, the weird part is that Dedicated VMs actually started correctly.



          I solved it by using the VM image to create a new VM, then a new IMAGE, and recreated the Azure Batch pool using this new image. The important part was not deleting the VM objects.






          share|improve this answer























          • One more thing so you know if you are trying to figure something out in Batch: Batch is buggy. Specially when using linux VMs. Ubuntu 1804 was completely broken for batch at least a few months ago(I'm using 1604).

            – Renato Fontes
            May 13 at 17:14













          0












          0








          0







          The problem was quite complicated, and probably a bug in Azure Batch.



          Some VM objects had been removed from the resource group by someone in the team. This caused Low Priority VMs to be unable to start, the weird part is that Dedicated VMs actually started correctly.



          I solved it by using the VM image to create a new VM, then a new IMAGE, and recreated the Azure Batch pool using this new image. The important part was not deleting the VM objects.






          share|improve this answer













          The problem was quite complicated, and probably a bug in Azure Batch.



          Some VM objects had been removed from the resource group by someone in the team. This caused Low Priority VMs to be unable to start, the weird part is that Dedicated VMs actually started correctly.



          I solved it by using the VM image to create a new VM, then a new IMAGE, and recreated the Azure Batch pool using this new image. The important part was not deleting the VM objects.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered May 13 at 17:08









          Renato FontesRenato Fontes

          63




          63












          • One more thing so you know if you are trying to figure something out in Batch: Batch is buggy. Specially when using linux VMs. Ubuntu 1804 was completely broken for batch at least a few months ago(I'm using 1604).

            – Renato Fontes
            May 13 at 17:14

















          • One more thing so you know if you are trying to figure something out in Batch: Batch is buggy. Specially when using linux VMs. Ubuntu 1804 was completely broken for batch at least a few months ago(I'm using 1604).

            – Renato Fontes
            May 13 at 17:14
















          One more thing so you know if you are trying to figure something out in Batch: Batch is buggy. Specially when using linux VMs. Ubuntu 1804 was completely broken for batch at least a few months ago(I'm using 1604).

          – Renato Fontes
          May 13 at 17:14





          One more thing so you know if you are trying to figure something out in Batch: Batch is buggy. Specially when using linux VMs. Ubuntu 1804 was completely broken for batch at least a few months ago(I'm using 1604).

          – Renato Fontes
          May 13 at 17:14

















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Server Fault!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f966789%2fazure-batch-low-priority-nodes-not-working-at-all%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Wikipedia:Vital articles Мазмуну Biography - Өмүр баян Philosophy and psychology - Философия жана психология Religion - Дин Social sciences - Коомдук илимдер Language and literature - Тил жана адабият Science - Илим Technology - Технология Arts and recreation - Искусство жана эс алуу History and geography - Тарых жана география Навигация менюсу

          Bruxelas-Capital Índice Historia | Composición | Situación lingüística | Clima | Cidades irmandadas | Notas | Véxase tamén | Menú de navegacióneO uso das linguas en Bruxelas e a situación do neerlandés"Rexión de Bruxelas Capital"o orixinalSitio da rexiónPáxina de Bruselas no sitio da Oficina de Promoción Turística de Valonia e BruxelasMapa Interactivo da Rexión de Bruxelas-CapitaleeWorldCat332144929079854441105155190212ID28008674080552-90000 0001 0666 3698n94104302ID540940339365017018237

          What should I write in an apology letter, since I have decided not to join a company after accepting an offer letterShould I keep looking after accepting a job offer?What should I do when I've been verbally told I would get an offer letter, but still haven't gotten one after 4 weeks?Do I accept an offer from a company that I am not likely to join?New job hasn't confirmed starting date and I want to give current employer as much notice as possibleHow should I address my manager in my resignation letter?HR delayed background verification, now jobless as resignedNo email communication after accepting a formal written offer. How should I phrase the call?What should I do if after receiving a verbal offer letter I am informed that my written job offer is put on hold due to some internal issues?Should I inform the current employer that I am about to resign within 1-2 weeks since I have signed the offer letter and waiting for visa?What company will do, if I send their offer letter to another company