Mir

[regression] Unresponsive/hung clients may never recover after waking up and could get disconnected

Bug #1370117 reported by Alexandros Frantzis on 2014-09-16
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Triaged
Low
Unassigned
mir (Ubuntu)
Low
Unassigned

Bug Description

After the merge [1], if a client is blocked and the socket becomes full, then:

1. if the server tries to send an event and it can't the event will be dropped
2. if the server tries to reply to an RPC call (e.g. next_buffer) and it can't, it will disconnect the client

We need to deal with the issue more gracefully, allowing clients to better recover from transient freezes. At the same time we need to have some mechanism to handle clients that are unresponsive for too long, so that we don't waste server-side resources.

[1] https://code.launchpad.net/~afrantzis/mir/fix-1350207-unresponsive-clients/+merge/233934

summary: - Gracefully handle clients that are transiently or permanently hung
+ [regression] Unresponsive/hung clients may never recover after waking up
+ and could get disconnected
tags: added: regression
Changed in mir:
status: New → Triaged
Changed in mir:
importance: High → Low
Michał Sawicz (saviq) wrote :

Syncing task from Mir.

Changed in mir (Ubuntu):
importance: Undecided → Low
status: New → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers