Alright, we are now ready to do this. New date: June 14 2018, around
14:00 UTC.
On Tue, Jun 5, 2018 at 9:31 AM, Andrew Otto <otto(a)wikimedia.org> wrote:
> Hi,
>
> We need to delay this switchover. We’ve made some changes to the plan
> that require a bit more prep work. Follow https://phabricator.
> wikimedia.org/T185225 for more details.
>
> I’ll reply with another announcement email when we set a new date.
>
> - Andrew Otto
> Senior Systems Engineer, WMF
>
>
>
> On Tue, May 15, 2018 at 11:43 AM, Andrew Otto <otto(a)wikimedia.org> wrote:
>
>> Hi all!
>>
>> *If you are not an active user of the EventStreams service, you can
>> ignore this email.*
>>
>> We’re in the process of upgrading
>> <https://phabricator.wikimedia.org/T152015> the backend infrastructure
>> that powers the EventStreams service. When we switch EventStreams to
>> the new infrastructure <https://phabricator.wikimedia.org/T185225>, the
>> ‘offsets’ AKA Last-Event-IDs will change.
>>
>> Connected EventStreams SSE clients will reconnect and not be able to
>> automatically consume from the exact position in the stream where they left
>> off. Instead, reconnecting clients will begin consuming from the latest
>> messages in the stream. This means that connected clients will likely miss
>> any messages that occurred during the reconnect period. Hopefully this
>> will be a very small number of messages, as your SSE client should
>> reconnect quickly.
>>
>> This switch is scheduled to happen on June 5 2018, at around 17:30 UTC.
>>
>> Let us know if you have any questions.
>>
>> Thanks!
>> - Andrew Otto
>> Senior Systems Engineer, WMF
>>
>>
>>
>>
>>
>>
>>
>>
>
Hi all!
*If you are not an active user of the EventStreams service, you can ignore
this email.*
We’re in the process of upgrading
<https://phabricator.wikimedia.org/T152015> the backend infrastructure that
powers the EventStreams service. When we switch EventStreams to the new
infrastructure <https://phabricator.wikimedia.org/T185225>, the ‘offsets’
AKA Last-Event-IDs will change.
Connected EventStreams SSE clients will reconnect and not be able to
automatically consume from the exact position in the stream where they left
off. Instead, reconnecting clients will begin consuming from the latest
messages in the stream. This means that connected clients will likely miss
any messages that occurred during the reconnect period. Hopefully this
will be a very small number of messages, as your SSE client should
reconnect quickly.
This switch is scheduled to happen on June 5 2018, at around 17:30 UTC.
Let us know if you have any questions.
Thanks!
- Andrew Otto
Senior Systems Engineer, WMF