Where to Work – AWS Elemental Conductor Live 3 or a Worker Node? - AWS Elemental Conductor Live 3

This is version 3.18 of the AWS Elemental Conductor Live 3 documentation. This is the latest version. For prior versions, see the Previous Versions section of AWS Elemental Conductor Live 3 Documentation.

Where to Work – AWS Elemental Conductor Live 3 or a Worker Node?

Guidelines:

  • Typically, you should run activity by creating channels and running them via AWS Elemental Conductor Live 3.

  • Avoid creating events on an AWS Elemental Live node that is part of an AWS Elemental Conductor Live 3 cluster. It is much better to create these channels on Conductor, because then Conductor will know about them and you can manage them through AWS Elemental Conductor Live 3.

  • Avoid creating an MPTS output on an AWS Elemental Live or an AWS Elemental Statmux node that is part of an AWS Elemental Conductor Live 3 cluster. Create them on Conductor so you can manage them through Conductor.

  • Create events only in special circumstances. For example, you may want to test a new encoding feature that is new to AWS Elemental Live, and you may want to test it in a clustered environment. In this case, you would create a temporary event on an AWS Elemental Live node.

  • Finally, and most importantly, the way that channels and events use their profiles is different. The way that channels use profiles has some distinct advantages in terms of visibility and maintenance. See Setting Up Profiles.

Working in AWS Elemental Live

When running activity in the AWS Elemental Live web interface, keep these points in mind:

  • From AWS Elemental Live, you can create events only using profiles that are local to the Live node. You cannot access profiles that were created in AWS Elemental Conductor Live 3.

  • Profiles created by AWS Elemental Live (“event profiles”) and those created by AWS Elemental Conductor Live 3 (“channel profiles”) have significant differences, so you will not be able to duplicate all the behavior of an Conductor profile from Live. See Setting Up Profiles.

  • The AWS Elemental Live web interface will show both events created locally on this node and channels created by AWS Elemental Conductor Live 3 and assigned to this node. Channels will be tagged “channel".

  • You can start and stop any event. Keep in mind that AWS Elemental Conductor Live 3 has no knowledge of an event or its status, so you will not be able to manage the event from Conductor. Events are not handled by any failover procedure.

  • You can modify a channel in AWS Elemental Live, but doing so has an impact on your audit trail.

  • You can stop any running channel from AWS Elemental Live (you cannot start a channel from Live). But we recommend that you not do this: instead, stop the channel from AWS Elemental Conductor Live 3. The only time you should stop a channel is in a false failure situation, because that is the only way to stop. For information on false failures, see How Worker Node Failover Occurs.

Modifying Channels via AWS Elemental Live

Typically, when you want to change the processing on a channel, you create a new profile in AWS Elemental Conductor Live 3 (possibly by duplicating then modifying the original profile) and associate the channel with that new profile. For details, see Modifying a Channel.

However, if either intentionally or accidentally, AWS Elemental Conductor Live 3 is offline, there is no way to change the channel-profile association “at the source”. If it is imperative that you change the channel immediately, you can make a quick fix by modifying the contents of the channel/event directly in AWS Elemental Live.

Note

We strongly recommend that you modify channel/events directly in AWS Elemental Live only as a last resort. And if you do modify directly, you should take steps to bring the channel “back into line” as soon as possible by changing the channel-profile association within the channel, from AWS Elemental Conductor Live 3.

Keep in mind that when you make direct changes to a channel/event:

  • The modification is local to this event only: it will not affect other channels or events in AWS Elemental Conductor Live 3 or AWS Elemental Live.

  • AWS Elemental Conductor Live 3 does not know about the modifications.

  • If you stop the modified channel from AWS Elemental Live and restart it, the channel continues to use the local changes.

  • If you stop the modified channel from AWS Elemental Conductor Live 3 and restart it, the local modifications are lost and the channel restarts with the original information from the profile.

  • If the node where the channel is running fails and the node is part of a redundancy group, then the following occurs: AWS Elemental Conductor Live 3 moves the channel over to another node. The local modifications are lost and the channel restarts with the original information from the profile

    If the node fails but the channel does not move to another node (for example, there are no reserve nodes available), then the channel may restart on the same node (if, for example, the node automatically recovers). In this case, the local modifications are preserved and the channel restarts with those modifications.

    For more information on failure and failover, see How Worker Node Failover Occurs.

  • If the node where the channel is running fails and the node is not part of a redundancy group, then the channel may restart on the same node (if, for example, the node automatically recovers). In this case, the local modifications are preserved and the channel restarts with those modifications.