Direct Traffic to one node in Cloud Service

Question

Is there a way to make a cloud service (web role) always use one of the nodes, there are two in this scenario, and only direct to the other one if the first one gets shut down. We have a piece of legacy software we use in our Cloud Service and we are waiting
on it being updated so it can work across the load balancer, but currently it does not. So we only have one node in the service. I would like to have two and see if we can always hit node 1 for example, and then hit node 2 if 1 is down. I am assuming, maybe
wrongly, that this would still be within SLA, and if maintenance was happening then both nodes would not get shutdown. Is it possible to maybe have a web role class which controls the load balancer traffic?
Thanks
Eamonn

Answer 1

Hi Eamonn,
Thanks for your posting!
>>Is there a way to make a cloud service (web role) always use one of the nodes, there are two in this scenario,...
Base on my experience, if we have one or more instances of a VM (Web or Worker role), the traffic will be distributed amongst the instances. We isn't allowed to specify which instances. Please see David's psot(http://stackoverflow.com/a/12726613
>> I would like to have two and see if we can always hit node 1 for example, and then hit node 2 if 1 is down. I am assuming, maybe.....
About this requirement, I suggest you could try to those steps:
1.create a web role with adding a web service or create a web role using WCF service.
2.create a service with the instance information, like this:
[WebMethod]
public ReturnResult ReverseString(string value)
ReturnResult rr = new ReturnResult();
rr.ReturnString = new string(value);
rr.HostName = RoleEnvironment.CurrentRoleInstance.Id;;
return rr;
//Class
public class ReturnResult
private String returnString;
public String ReturnString
get { return returnString; }
set { returnString = value; }
private String hostName;
public String HostName
get { return hostName; }
set { hostName = value; }
3.Host this service on azure cloud service
4.Create a new project whatever it is webpage or console application.
5.using the Thread Pool or BackgroundWorker to send the concurrent request.
6.Check the results list and host name.
After made it, you could get the every requests hot which instances .
If you'd like to custom the Azure loadbalancer, I recommend you could refer to those documents:
http://msdn.microsoft.com/en-us/library/azure/jj151530.aspx
http://blogs.msdn.com/b/kdot/archive/2013/06/29/implementing-custom-load-balancing-with-sticky-connections-on-windows-azure.aspx
Regards,
Will
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.