[JIRA] (JENKINS-15473) Jenkins forgets about old builds under IO pressure

Eric Fleischman created JENKINS-15473

Jenkins forgets about old builds under IO pressure

Issue Type:	Bug
Affects Versions:	current
Assignee:	Unassigned
Components:	status-view
Created:	11/Oct/12 2:17 AM
Description:	I am a pretty small Jenkins install. Single win2k8 R2 VM running all Jenkins roles doing 1-2 builds/hour. 2 branches. Full build execution time (which is mostly tests running) is ~6 minutes. I have found that when under IO pressure, Jenkins fails to load historical builds for my branches. I have observed this in two scenarios: 1) Service start after boot (when OS services are still coming up) 2) If it tries to load this data when a build is execution (which is typically I/O bound) it will "forget" all of this data. When this happens, either restarting the Jenkins service or triggering "reload config" from the manage Jenkins UI will cause it to reload this data and all is well again. If there are logs of interest let me know and I'm happy to collect them. I'm a n00b so not sure what would be helpful. I'm starting to collect diagnostic data in parallel (reading up on what would be helpful)...
Environment:	Jenkins 1.485 Windows Server 2008 R2 JVM 1.6.0_31 with vendor == Sun Running Jenkins as an NT service as local Administrator OS running in a virtual machine with 2GB RAM & a few logical procs (on under-utilized host)
Project:	Jenkins
Priority:	Major
Reporter:	Eric Fleischman

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Eric Fleischman updated JENKINS-15473

Jenkins forgets about old builds under IO pressure

Change By:

Eric Fleischman (11/Oct/12 2:32 AM)

Description:

I am a pretty small Jenkins install. Single win2k8 R2 VM running all Jenkins roles doing 1-2 builds/hour. 2 branches. Full build execution time (which is mostly tests running) is ~6 minutes. I have found that when under IO pressure, Jenkins fails to load historical builds for my branches. I have observed this in two scenarios: 1) Service start after boot (when OS services are still coming up) 2) If it tries to load this data when a build is execution (which is typically I/O bound) it will "forget" all of this data. When this happens, either restarting the Jenkins service or triggering "reload config" from the manage Jenkins UI will cause it to reload this data and all is well again. I have seen this at rare occasions in the past but it has gotten materially more frequent over the last few upgrades (I tend to stay up to date with the latest Jenkins builds). Over the last couple of weeks it has become a near daily issue. If there are logs of interest let me know and I'm happy to collect them. I'm a n00b so not sure what would be helpful. I'm starting to collect diagnostic data in parallel (reading up on what would be helpful)...

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Eric Fleischman updated JENKINS-15473

Jenkins forgets about old builds under IO pressure

Change By:

Eric Fleischman (11/Oct/12 6:49 PM)

Description:

I am a pretty small Jenkins install. Single win2k8 R2 VM running all Jenkins roles doing 1-2 builds/hour. 2 branches. Full build execution time (which is mostly tests running) is ~6 minutes. I have found that when under IO pressure, Jenkins fails to load historical builds for my branches. I have observed this in two scenarios: 1) Service start after boot (when OS services are still coming up) 2) If it tries to load this data when a build is execution (which is typically I/O bound) it will "forget" all of this data. When this happens, either restarting the Jenkins service or triggering "reload config" from the manage Jenkins UI will cause it to reload this data and all is well again. I have seen this at rare occasions in the past but it has gotten materially more frequent over the last few upgrades (I tend to stay up to date with the latest Jenkins builds , I upgrade ~weekly ). Over the last couple of weeks it has become a  near  ~  daily issue , typically triggered during build execution . If there are logs of interest let me know and I'm happy to collect them. I'm a n00b so not sure what would be helpful. I'm starting to collect diagnostic data in parallel (reading up on what would be helpful)...

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Eric Fleischman commented on JENKINS-15473

Jenkins forgets about old builds under IO pressure

Perhaps related to this recent feature? https://issues.jenkins-ci.org/browse/JENKINS-8754

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Jesse Glick assigned JENKINS-15473 to Kohsuke Kawaguchi

Jenkins forgets about old builds under IO pressure

Change By:	Jesse Glick (15/Oct/12 6:55 PM)
Assignee:	Kohsuke Kawaguchi

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Kohsuke Kawaguchi resolved JENKINS-15473 as Duplicate

Jenkins forgets about old builds under IO pressure

Dupliate of JENKINS-15465
Change By:	Kohsuke Kawaguchi (15/Oct/12 7:02 PM)
Status:	Open Resolved
Resolution:	Duplicate

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira