Project

General

Profile

Actions
Copy link

Bug #20875

closed

max_memory_per_executor can lead to stuck executor, waiting for an event that would not arrive

Added by Ivan Necas about 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Ivan Necas
Category:
Dynflow
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
1434069
Pull request:
https://github.com/Dynflow/dynflow/pull/250
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

We should have a timeout after which we will not wait any longer and just terminate the world.

Reproduced by:

1. setting the memory limit on executor
2. triggering remote execution on 1000 fake hosts so that the memory crosses the limit
3. the task gets paused, but the executor doesn't finish running

Related issues 1 (0 open — 1 closed)

Related to foreman-tasks - Feature #17175: max_memory_per_executor supportClosedShimon Shtein11/01/2016Actions
Actions
Copy link
 #1

Updated by Ivan Necas about 7 years ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by Ivan Necas about 7 years ago

Actions
Copy link
 #3

Updated by Ivan Necas about 7 years ago

  • Bugzilla link set to 1434069
Actions
Copy link
 #4

Updated by Ivan Necas about 7 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/Dynflow/dynflow/pull/250 added
Actions
Copy link
 #5

Updated by Adam Ruzicka about 7 years ago

  • Status changed from Ready For Testing to Closed
Actions
Copy link

Also available in: Atom PDF