By incomplete, for clarity, we mean production rows are not getting
through, only rows from the labs instance.

Erik, will the fix stream in just new rows or are the old rows cached
somewhere? I expect the former.

On 19 January 2016 at 11:25, Erik Bernhardson

<ebernhardson@wikimedia.org> wrote:
> It looks like there have been some issues in CirrusSearch since the train
> rolled forward last thursday, the 14th. Our logs to hadoop have been
> incomplete. This will be fixed in ~ 5 hours during the evening SWAT deploy.
>
> On Tue, Jan 19, 2016 at 11:23 AM, Tomasz Finc <tfinc@wikimedia.org> wrote:
>>
>> thanks for the heads up
>>
>> On Tue, Jan 19, 2016 at 10:44 AM, Oliver Keyes <okeyes@wikimedia.org>
>> wrote:
>> > Hey all,
>> >
>> > You might notice some weird spikes in the dashboard data. This is
>> > caused by some duplicated days worth of data due to the stop-and-start
>> > of services we're dependent on. We expect to have it resolved by the
>> > end of the day.
>> >
>> > Thanks!
>> >
>> > --
>> > Oliver Keyes
>> > Count Logula
>> > Wikimedia Foundation
>> >
>> > _______________________________________________
>> > discovery mailing list
>> > discovery@lists.wikimedia.org
>> > https://lists.wikimedia.org/mailman/listinfo/discovery
>>
>> _______________________________________________
>> discovery mailing list
>> discovery@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/discovery
>
>
>
> _______________________________________________
> discovery mailing list
> discovery@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/discovery
>



--
Oliver Keyes
Count Logula
Wikimedia Foundation

_______________________________________________
discovery mailing list
discovery@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/discovery