There were some issues over the weekend and we transitioned everyone back to the main cluster.
This morning, we’ll collect a list of tasks to complete before we start moving non-Staff accounts over to the AWS cluster. After we have that, we’ll get a better idea of when we can expect the first batch of partners to transition.
Before we transition any partners, we’ll enable the new cluster on the staff accounts again.
Is there any way to get a list of impacted users made public (When you are about to launch), so we can validate that our processes correctly switch over (so automatic detection vs what is actually expected) - That way we can flag/give feedback about issues we see as third parties?
My own migration plan is to join all 3 clusters (main, event, aws).
That avoids needing to call /chat_properties for every room join, and avoids needing to worry about which cluster to join/when to join a cluster.
Would it be possible to get a heads up the day before (weekday before?) the migration happens?That way if you plan to do it at night or over the weekend I can plan to be on watching to make sure my processes migrate smoothly? Would love you long time for it <3
Just an update, I’m deploying a change to drop messages that are “sent from the wrong side of the AWS fence” in preparation for the migration.
In other words, a message sent to a channel on the “aws” cluster to a server not on AWS (e.g. irc.twitch.tv) will be dropped. Similarly, a message sent to a channel not on the “aws” cluster to a server on AWS (e.g. irc.chat.twitch.tv) will be dropped.
Bots can do one of two things to make sure they send messages to the right server:
We’re planning to shift a small number of partners to the new cluster later today for testing. Be sure to implement one of the two solutions @arcoraven posted above! If we run into any problems, we’ll reach out to help get you connected.
We’re still gathering a list of volunteers – we expect around 10-20 will be included in this test. Once this test concludes, we’ll start migrating people over in larger numbers. So, no list of users yet, but if you’re connected to the new cluster you’re good to go!
There’s no benefits to you (only to Twitch), but there are downsides (like third party tools like bots or alerts being incompatible). If you use any of my tools, I’ve spent today integrating support for this change so it should be a seamless switchover for anyone who opts in.