[Swift-user] understanding coaster service logs

[Allan Espinosa]

Hi,

My coaster services are registering 1.2k CPUs at a time.  Yet my jobs
does not seem to get sent to some workers:

Progress:  Selecting site:2762  Submitted:580  Finished
successfully:424 Failed but can retry:138
Progress:  Selecting site:2762  Submitted:580  Finished
successfully:424 Failed but can retry:138

It maybe the case that my workers only has outbound connections and no inbound?

Which coaster-service log entries should I look out for to know if (1)
a job is received and (2) a job is dispatched to a worker (3) blockID
the job was sent to?

Does <Block-ID>: pull refer to a worker receiving a job?

SC-null: Disabling heartbeats (config is null)
(0) Scheduling SC-null for addition
nullChannel started
Received registration: blockid = Prairiefire, url =
MetaChannel: 835803672[661780277: {}] -> null: Disabling heartbeats
(config is null)
MetaChannel: 835803672[661780277: {}] -> null.bind -> SC-null
Started CPU 397:1287509763s
Started worker Prairiefire:000397
Prairiefire:397 pull
Plan time: 1
Plan time: 1
Plan time: 1
Plan time: 1
Plan time: 1
Sender 799611093 queue size: 0
Sender 1237174744 queue size: 0
runTime: 54, sleepTime: 9993
Avg stream buf: 0
runTime: 6, sleepTime: 10003
Plan time: 1
Plan time: 1
Plan time: 1
Plan time: 1
Plan time: 1
Plan time: 1
Avg stream buf: 0
Sender 1191940729 queue size: 0
Sender 1231426791 queue size: 0
No streams
Sender 1191940729 queue size: 0
Sender 2128911821 queue size: 0
Avg stream buf: 0
No streams
Avg stream buf: 0
Plan time: 1


-- 
Allan M. Espinosa <http://amespinosa.wordpress.com>
PhD student, Computer Science
University of Chicago <http://people.cs.uchicago.edu/~aespinosa>