Twist component with all its importance tends to get hung regularly causing job failures and user login issues. In large multi-core multi-mesh environments, with load balanced twist, this becomes a challenge to identify the hung connection in a specific slice. The troubleshooting is time consuming and inaccurate with all ambiquity in the twist logs around twist connection data.
Is there a way we can monitor existing local twist connections or component proceses real time and be alerted or atleast have an entry in logs pointing the slice with the issue. It not only helps us in fixing the issue quickly but could be useful to fix it permanently as we know the frequency of the issue on same slices.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.