|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #60877 no way to set client_id for a GearmanWorker
Submitted: 2012-01-25 11:54 UTC Modified: 2012-08-06 04:34 UTC
From: sendrossemail+php at gmail dot com Assigned: hradtke (profile)
Status: Closed Package: gearman (PECL)
PHP Version: Irrelevant OS: linux*
Private report: No CVE-ID: None
 [2012-01-25 11:54 UTC] sendrossemail+php at gmail dot com
Hi there, firstly thanks for this package!

From what I can see of the docs there does not appear to be a means to set the Worker client_id (part of the gearman spec).

Most other languages allow the setting of this id (which is very useful when writing a gearman monitoring suite)

I am considering modifying the extension myself, however would like to hear if its a feasible fix (or change depending how you view it).


Expected result:
client_id: <-- python worker
tasks: ('reverse',)

client_id: TestWorker.php <-- php woker
tasks: ('reverse')

Actual result:
client_id: <-- python worker
tasks: ('reverse',)

client_id: - <-- php worker - as u can see - is the id which is no good when multiple of the same worker is registered
tasks: ('reverse')


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2012-02-02 06:17 UTC]
I don't see an option in libgearman to set the client it. I am going to ask Brian 
Aker about why this is.

The python library can do this because it does not use libgearman, but instead 
interfaces with the gearman server directly.
 [2012-02-02 06:17 UTC]
-Status: Open +Status: Assigned -Assigned To: +Assigned To: hradtke
 [2012-02-02 06:23 UTC]
I take it back. This was just added in libgearman 0.26.
 [2012-08-06 04:34 UTC]
 [2012-08-06 04:34 UTC]
-Status: Assigned +Status: Closed
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Sun Jul 14 15:01:28 2024 UTC