# OpenVidu Pro Inspector - add media nodes

**URL:** <https://openvidu.discourse.group/t/openvidu-pro-inspector-add-media-nodes/2441>\
**Category:** Issues with deployment\
**Tags:** v2\
**Created:** [December 15, 2020, 6:52pm UTC](https://openvidu.discourse.group/t/openvidu-pro-inspector-add-media-nodes/2441 "2020-12-15T18:52:56Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![DaveNascimento](https://avatars.discourse-cdn.com/v4/letter/d/a5b964/32.png) [@DaveNascimento](https://openvidu.discourse.group/u/DaveNascimento)\
**Post date:** [December 15, 2020, 6:52pm UTC](https://openvidu.discourse.group/t/openvidu-pro-inspector-add-media-nodes/2441/1 "2020-12-15T18:52:56Z")

</div>

On a standard AWS OpenVidu Pro deployment with 8 media nodes, only 1 shows up on the Cluster screen. If I try to add a media node manually, it shows up briefly on the screen but then disappears.

Is this normal behaviour? Is the node disappearing because it’s not required at that moment (loads on the active media node are less than 1%)?

---

<div class="post-metadata">

**Author:** ![cruizba](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/cruizba/32/18_2.png) [@cruizba](https://openvidu.discourse.group/u/cruizba)\
**Post date:** [December 16, 2020, 9:42am UTC](https://openvidu.discourse.group/t/openvidu-pro-inspector-add-media-nodes/2441/2 "2020-12-16T09:42:50Z")

</div>

It depends. Do you have autoscaling enabled?

Regards,  
Carlos

---

<div class="post-metadata">

**Author:** ![DaveNascimento](https://avatars.discourse-cdn.com/v4/letter/d/a5b964/32.png) [@DaveNascimento](https://openvidu.discourse.group/u/DaveNascimento)\
**Post date:** [December 16, 2020, 10:04am UTC](https://openvidu.discourse.group/t/openvidu-pro-inspector-add-media-nodes/2441/3 "2020-12-16T10:04:15Z")

</div>

No, but OPENVIDU\_PRO\_CLUSTER\_MODE is defined as “auto” in .env (AWS deployment default).  
Could this be the problem?

![Screenshot 2020-12-16 at 10.01.50](https://global.discourse-cdn.com/free1/uploads/openvidu/original/2X/6/6a9a195e6057e6c1024300deb5b6babb134b912b.png)

 ![Screenshot 2020-12-16 at 10.03.51](https://global.discourse-cdn.com/free1/uploads/openvidu/original/2X/e/e7e369172fdcd49de7d56cb3e42d9073fd6ae36d.png)

---

<div class="post-metadata">

**Author:** ![cruizba](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/cruizba/32/18_2.png) [@cruizba](https://openvidu.discourse.group/u/cruizba)\
**Post date:** [December 16, 2020, 10:10am UTC](https://openvidu.discourse.group/t/openvidu-pro-inspector-add-media-nodes/2441/4 "2020-12-16T10:10:26Z")

</div>

Yes, this is a problem. Did you change anything of the .env file? Can you show the log of openvidu when a new media node is launched?

Regards,  
Carlos

---

<div class="post-metadata">

**Author:** ![DaveNascimento](https://avatars.discourse-cdn.com/v4/letter/d/a5b964/32.png) [@DaveNascimento](https://openvidu.discourse.group/u/DaveNascimento)\
**Post date:** [December 16, 2020, 10:57am UTC](https://openvidu.discourse.group/t/openvidu-pro-inspector-add-media-nodes/2441/5 "2020-12-16T10:57:47Z")

</div>

I didn’t touch the .env file, but changed the max and min bitrates with the inspector config tab. The only thing I notice in the logs are several (dozens) of calls to the /media-nodes endpoint whenever I try to launch a new media node.

 ![Screenshot 2020-12-16 at 10.54.08](https://global.discourse-cdn.com/free1/uploads/openvidu/original/2X/d/db09dad153faf25b4c2933fcfe462a1caf90beda.png)

It may just be something wrong with the parameters set in the AWS yaml file.  
Should I change OPENVIDU\_PRO\_CLUSTER\_MODE to manual to solve the problem on my side?

---

<div class="post-metadata">

**Author:** ![cruizba](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/cruizba/32/18_2.png) [@cruizba](https://openvidu.discourse.group/u/cruizba)\
**Post date:** [December 16, 2020, 11:01am UTC](https://openvidu.discourse.group/t/openvidu-pro-inspector-add-media-nodes/2441/6 "2020-12-16T11:01:59Z")

</div>

Yes, that’s the inspector receiving information about the cluster.

No, don’t change it to manual.

Regards,  
Carlos

---

<div class="post-metadata">

**Author:** ![cruizba](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/cruizba/32/18_2.png) [@cruizba](https://openvidu.discourse.group/u/cruizba)\
**Post date:** [December 16, 2020, 11:27am UTC](https://openvidu.discourse.group/t/openvidu-pro-inspector-add-media-nodes/2441/7 "2020-12-16T11:27:31Z")

</div>

It was a problem related with vCPU limit in AWS.

```auto
Unknown error An error occurred (VcpuLimitExceeded) when calling 
the RunInstances operation: You have requested more vCPU capacity
 than your current vCPU limit of 32 allows for the instance bucket that
 the specified instance type belongs to.
 Please visit http://aws.amazon.com/contact-us/ec2-request to request an adjustment to this limit.

```

Problem probably can be solved requesting limit changes to aws in [http://aws.amazon.com/contact-us/ec2-request](http://aws.amazon.com/contact-us/ec2-request).

Marking this as solution at the moment.

Please @DaveNascimento, update with a post when the problem is solved.

Regards,  
Carlos

---

<div class="post-metadata">

**Author:** ![DaveNascimento](https://avatars.discourse-cdn.com/v4/letter/d/a5b964/32.png) [@DaveNascimento](https://openvidu.discourse.group/u/DaveNascimento)\
**Post date:** [December 21, 2020, 11:39pm UTC](https://openvidu.discourse.group/t/openvidu-pro-inspector-add-media-nodes/2441/8 "2020-12-21T23:39:59Z")

</div>

Problem solved: asked AWS for a EC2 vCPU quota increase a few days ago and got an approval, media nodes were available to launch manually as expected. Thank you for your assistance, @cruizba!
