Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deleting a netbox makes data-collection stop #1403

Closed
jmbredal opened this issue Jan 17, 2017 · 1 comment
Closed

deleting a netbox makes data-collection stop #1403

jmbredal opened this issue Jan 17, 2017 · 1 comment
Assignees
Labels
Milestone

Comments

@jmbredal
Copy link
Collaborator

jmbredal commented Jan 17, 2017

When deleting a netbox the table ipdevpoll_job_log seems to be locked for updates. As every ipdevpoll job wants to update this table they all is kept waiting when the delete takes a long time.

Related reference in local ticket system:
https://rt.uninett.no/Ticket/Display.html?id=115204


Imported from Launchpad using lp2gh.

@lunkwill42
Copy link
Member

lunkwill42 commented Feb 1, 2017

Observing this again now. It seems that what may actually be happening here is that while PostgreSQL is running cascading deletes, ipdevpoll still doesn't know that the netbox in question is being deleted, so the jobs related to this device are still running. Any attempt to insert an ipdevpoll_job_log entry related to this netbox will be blocked by PostgreSQL, eventually causing all available database connections in an ipdevpoll process to be blocked.

One suggested solution would be to introduce a deletion flag on netbox, which would cause ipdevpoll to stop working on it. This overlaps with one of the discussed solutions for #1313.

@lunkwill42 lunkwill42 added this to the 4.7.0 milestone Feb 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants