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.

Sign up for GitHub

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

Jump to bottom

Stale Status #1642

Closed
JohnPTobe opened this issue May 29, 2019 · 1 comment · Fixed by #1655
Closed

Stale Status #1642

JohnPTobe opened this issue May 29, 2019 · 1 comment · Fixed by #1655
Assignees
@JohnPTobe
Labels
bug rest api scheduler
Milestone
Sprint 1

Comments

@JohnPTobe
Copy link

The status api in our dev cluster returns no content because the timestamp is over 12 seconds old (between 30-40). We need to either fix whatever is slowing down status generation or increase the freshness threshold.
@JohnPTobe
Copy link
Author

The problem seems to be the get_title() and get_description() methods when populating job types' status. Setting title/description attributes when syncing with the database and using them instead should speed it up.

@JohnPTobe JohnPTobe self-assigned this May 29, 2019
@JohnPTobe JohnPTobe added this to the Sprint 1 milestone May 29, 2019
JohnPTobe pushed a commit that referenced this issue Jun 3, 2019
⚡ Fixing stale status (#1642)
0865b57
@JohnPTobe JohnPTobe mentioned this issue Jun 3, 2019
Merged
4 tasks
JohnPTobe pushed a commit that referenced this issue Jun 10, 2019
Merge pull request #1655 from ngageoint/1149-ClearDB
2f25dd6 
Fixes #1149 - Clear out database update
Fixes #1055. Fixes #1642. Fixes #1658. Fixes #1659.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JohnPTobe JohnPTobe

Labels
bug rest api scheduler
Projects
None yet
Milestone
Sprint 1
Development

Successfully merging a pull request may close this issue.

#1149 - Clear out database update ngageoint/scale
1 participant
@JohnPTobe