Robert et al, In contrast to your statement below, streaming of results from new or existing measurements using Magellan currently does *not* work… no results are obtained, see below.
—- [32mLooking good! Measurement 60182213 was created and details about it can be found here: https://atlas.ripe.net/measurements/60182213/[0m [32mConnecting to stream...[0m [32mDisconnected from stream[0m —- Regards, Ernst J. Oud > On 20 Sep 2023, at 07:43, Robert Kisteleki <[email protected]> wrote: > > > >> On 2023-09-19 23:04, Ernst J. Oud wrote: >> Considering the fact that all of Atlas is completely down for more than 24 >> hrs., I find the silence a bit deafening. No status updates, nothing. Weird. >> Not up to RIPE standards. >> Regards, >> Ernst J. Oud > > Good morning, > > I'm sad to report that indeed there's still an issue with result processing - > which is still reflected on the status page. > > Specifically, the HBase backend that is responsible for storing and > retrieving the new (and historic) results is struggling to store the data > form the last ~24 hours. The teams have been working on solving this > basically 24/7 since the issue occurred but haven't been successful yet. > > All else (continuing to run existing measurements, creating new ones, > real-time streaming of the results, APIs, UI, ...) are running undisturbed. > > I hope this helps understanding the extent of the problem, and we'll of > course let you know when there's progress. > > Regards, > Robert -- ripe-atlas mailing list [email protected] https://lists.ripe.net/mailman/listinfo/ripe-atlas
