search

gerritjvv / bigstreams

bigstreams big data kafka hadoop and file based imports
Eclipse Public License 1.0
3 stars 3 forks source link

Agent File Lock error logging #12

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
The agent should recognized a file lock error i.e. when the collector sent a 
request and the coordination service told the server that the current file has 
already been locked. On such an error the agent should include an informative 
error line in the log files. This will allow to track better why two requests 
from the same agent happen for the same file.

Original issue reported on code.google.com by gerritjvv@gmail.com on 27 Sep 2010 at 4:00

GoogleCodeExporter commented 8 years ago 
There is another possibility of conflict sending on lock conditions.
of why all this Locked already errors are hapening.
So:
Thread1:
Poll directory add every updated file to Queue (file)
Thread [ 2,3,4,5]  == directory threads. :
So that if thread1 is putting on the queue a file that Thread2 is already 
sending.

Original comment by gerritjvv@gmail.com on 26 Apr 2011 at 2:36

GoogleCodeExporter commented 8 years ago

Original comment by gerritjvv@gmail.com on 20 Jun 2011 at 8:14