Conversation

Notices

1. Suji Yan (sujiyan@mstdn.jp)'s status on Saturday, 18-Jul-2020 14:21:51 JST Suji Yan

   • のえる

   Around 5hrs ago we noticed multiple suspicious ‘remote delete request’ jammed JP’s pull queue from Mstdn.io (thanks for the notification from @noellabo https://twitter.com/noellabo/status/1284272898589339648?s=21 ) . This problem is fixed but we haven’t figure out the reason for the mstdn.io remote request.

   • のえる repeated this.
   • のえる (noellabo@fedibird.com)'s status on Saturday, 18-Jul-2020 15:10:15 JST のえる

     in reply to

     • Stanislas :NotLikeThis:
     • e-al
     • Normandy ⚡

     @Sujiyan @normandy @angristan @eal I do not know if this case corresponds to the following cases. For your reference.

     I also had a "Delete Activity Storm" on fedibird.com. At first, I thought it was coming repeatedly from the origin of the Delete Activity, but it wasn't.

     This was due to an exception that occurred when the Delete Actor's Delete Activity was being verified because the target Actor no longer exists and Sidekiq would retry the job.

   • Suji Yan (sujiyan@mstdn.jp)'s status on Saturday, 18-Jul-2020 15:10:16 JST Suji Yan

     in reply to

     • Stanislas :NotLikeThis:
     • e-al
     • Normandy ⚡

     @normandy @angristan @eal very likely. Might need to limit mass request since it will obviously jam JP’s queue

   • Normandy ⚡ (normandy@biribiri.dev)'s status on Saturday, 18-Jul-2020 15:10:22 JST Normandy ⚡

     in reply to

     • Stanislas :NotLikeThis:
     • e-al
     @eal @Sujiyan @angristan my guess is that someone (or an admin) deleted their account or were otherwise mass deleting their posts.
   • e-al (eal@social.sakamoto.gq)'s status on Saturday, 18-Jul-2020 15:10:24 JST e-al

     in reply to

     • Stanislas :NotLikeThis:
     • のえる
     @Sujiyan @noellabo cc @angristan
   • Suji Yan (sujiyan@mstdn.jp)'s status on Saturday, 18-Jul-2020 15:10:25 JST Suji Yan

     in reply to

     • のえる

     @Sujiyan @noellabo It will be very helpful if Mstdn.io ‘s admin could take a look into this and contact us as well. Thanks.

   • のえる (noellabo@fedibird.com)'s status on Saturday, 18-Jul-2020 15:10:31 JST のえる

     in reply to

     • Stanislas :NotLikeThis:
     • e-al
     • Normandy ⚡

     @Sujiyan @normandy @angristan @eal The deleted account will be held for a while to meet these verifications. However, it will be deleted when the deadline expires. The server may go offline. It may be delayed in response to the deletion and may not be in time. A retry that has been sleeping for a long time also occurs when you manually retry it.

   • のえる (noellabo@fedibird.com)'s status on Saturday, 18-Jul-2020 15:10:40 JST のえる

     in reply to

     • Stanislas :NotLikeThis:
     • e-al
     • Normandy ⚡

     @Sujiyan @normandy @angristan @eal ActivityPub::ProcessingWorker must not be present in sidekiq retries if the user or server has been deleted. Also, this worker is unlikely to succeed on retry, so it may be better to remove it uniformly from retries.