Runner runner timeout not working right

Bug #1570798 reported by Roman Vasilets
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Rally
Fix Released
High
Roman Vasilets

Bug Description

Running the following config:
   Authenticate.keystone:
   -
     runner:
       type: "rps"
       times: 300
       timeout: 5
       rps: 15
     context:
       users:
         tenants: 1
         users_per_tenant: 1

I've got http://paste.openstack.org/show/494196/ The trace is even bigger but it duplicates

After the research I found that this was cause by wrong assumption that Thread idents are unique but Thread identifiers may be recycled when a thread exits and another thread is created.

Changed in rally:
assignee: nobody → Roman Vasilets (rvasilets)
Revision history for this message
Roman Vasilets (rvasilets) wrote :

I have detect the exact reason. Its related to ability of python threads to recycle ids of the threads. Now I am going to fix it=)

Changed in rally:
importance: Undecided → Medium
summary: - Runner timeout not working when load duration bigger then it
+ Runner runner timeout not working right
description: updated
Changed in rally:
importance: Medium → High
status: New → Incomplete
status: Incomplete → Triaged
Changed in rally:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to rally (master)

Reviewed: https://review.openstack.org/314536
Committed: https://git.openstack.org/cgit/openstack/rally/commit/?id=5c4956cafbef6935d890c82a04d3e4e51033dca9
Submitter: Jenkins
Branch: master

commit 5c4956cafbef6935d890c82a04d3e4e51033dca9
Author: Roman Vasilets <email address hidden>
Date: Tue May 10 15:17:54 2016 +0300

    Fix runner timeout

    Decided to put thread instance to timeout_queue because
    thread.ident in python is recycled. So this is the way to
    check whether the thread alive or not.

    Closes-bug: #1570798

    Change-Id: I745030ec9942c37b47c6d53864ae5fc7ecae7ccd

Changed in rally:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.