maybe the "cool" line is this 

   - all other scheduler_task columns can be passed as keyword arguments; 
   the most important are shown.


however..... a task has group_name (it can be assigned to one and only one 
group), while the scheduler has group_names (multiple groups allowed).
if you start the scheduler with web2py.py -K appname the "group_names" are 
the same specified in the scheduler instantiation.
if you start it with web2py.py -K appname:group1:group2 it doesn't matter 
how you instantiated it, it will only process tasks assigned to either 
group1 or group2

On Wednesday, May 21, 2014 4:49:46 PM UTC+2, DeanK wrote:
>
> Yes I did read the docs several times.  And I'm not doubting you since you 
> have been right every time I've asked a question haha...but I still don't 
> see it.  From the documentation the prototype when scheduling a task is:
>
> scheduler.queue_task(
>     function,
>     pargs=[],
>     pvars={},
>     start_time=now,             #datetime
>     stop_time = None,           #datetime
>     timeout = 60,               #seconds
>     prevent_drift=False,
>     period=60,                  #seconds
>     immediate=False,
>     repeats = 1
> )
>
>
> I don't see anywhere a mention on how you set the group_names parameter.
>
>
>
> On Wednesday, May 21, 2014 3:30:42 AM UTC-4, Niphlod wrote:
>>
>> You can pass group names with the -K argument, when you start the 
>> process. When you queue a task, you must pass in the group_name parameter 
>> to "reserve" that task for a specific worker.
>>
>>
>> BTW: did you at least tried to read 
>> http://web2py.com/books/default/chapter/29/04/the-core#web2py-Schedulerbefore
>>  asking ?
>>
>>
>> On Tuesday, May 20, 2014 9:46:39 PM UTC+2, DeanK wrote:
>>>
>>> I'm looking to use the built in scheduler to farm out work, but run gpu 
>>> dependent code.  Because of this I need to be able to control on which node 
>>> the task is scheduled.  I thought I could do this using "groups" but I 
>>> don't see how since you set the group in the scheduler constructor 
>>> according to the docs?  I was expecting you would set groups that workers 
>>> are "subscribed" to when you start them on each node and then when you 
>>> schedule a task you can set which group the task is assigned to.  Is this 
>>> not possible or have I misinterpreted the documentation?
>>>
>>> scheduler.py in models:
>>>
>>> def my_task1():
>>>    #my first task
>>>
>>> def my_task2():
>>>    #another task
>>>
>>> from gluon.scheduler import Scheduler
>>>
>>> db_sched = 
>>> DAL('mysql://XXXX:XXXXX@XXXXX/XXXX',pool_size=8,check_reserved=['mysql'],migrate=True,fake_migrate_all=False,lazy_tables=False)
>>> scheduler = Scheduler(db_sched,heartbeat=2)
>>>
>>>
>>>
>>>

-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to