Job Id's Colide due to lack of system entropy

GoogleCodeExporter commented 9 years ago

The random generator in crypto/rand produces strings of non random characters 
when it runs out entropy which will will eventually produce a job id collision. 

Example:
scheme: https host: glados.systemsbiology.net port: 8083
{
   "FirstCreated": "Tue Aug 23 17:10:41 PDT 2011",
   "JobId": "1a9058d2000000000000000000000000",
   "Label": "1a9058d2000000000000000000000000",
   "LastModified": "",
   "Owner": "Anonymous",
   "Progress": {
       "Errored": 0,
       "Finished": 0,
       "Total": 100
   },
   "Running": false,
   "Scheduled": false,
   "Type": "Unspecified",
   "Uri": "/jobs/1a9058d2000000000000000000000000"
}

It is not clear if this is an issue with the server configuration or golang.

Original issue reported on code.google.com by ryanbres...@gmail.com on 24 Aug 2011 at 12:49

GoogleCodeExporter commented 9 years ago

Original comment by ryanbres...@gmail.com on 24 Aug 2011 at 12:52

GoogleCodeExporter commented 9 years ago

This is a system configuration error. It was being caused by low entropy 
production on the servers and hadoop's use of buffered io to load random 
numbers draining the entropy pool.

Original comment by ryanbres...@gmail.com on 1 Dec 2011 at 8:23

Changed state: Done

ryanbressler / golem

Job Id's Colide due to lack of system entropy #25