Unique task id available ?

[sprenge]

I am looking for a way to assign to each task instance a unique number (starting from zero for instance), this should be cluster unique (no overlapping numbers between slaves).
For the test case I am running it is required to have unique credentials for each task instance. Is this possible with locustio ?

[andrej-talon]

I would be interested in an answer as well. I saw that the Runner class has a number that could be used, but haven't been able to access it.

Currently, I solved it by using itertools.counter and advance it each time a request is made. However, it would be nice to expose the "real" number somehow.

[sprenge]

I assume that the trick with itertools.counter only works within a single process ? I solved it implementing a global webservice (using Flask), returning a unique counter id

[brentsmyth]

Anyone have any more luck here in terms of a distributed setup?

[worldmind]

I am not sure, but may it helps - I found this question on SO, it shows how make unique user, for unique task id you can use something like it with PostgreSQL sequence for getting IDs.

[cyberw]

Closed due to inactivity.