collection stopped/restarted and is missing history #42

Open
meghnas opened this Issue Aug 9, 2015 · 3 comments

Comments

Projects
None yet
1 participant
@meghnas
Collaborator

meghnas commented Aug 9, 2015

As reported by Ingmar Webber:

  1. The collection was started 4 days ago, but collection description shows last started: yesterday
  2. Collection history shows 45 tweets were collected and start and end date are equal
  3. Total collected tweets says 20k tweets, but it should be much more by now
@meghnas

This comment has been minimized.

Show comment
Hide comment
@meghnas

meghnas Aug 10, 2015

Collaborator

On Thursday, we had a new release of AIDR (v2.0), which required stopping all collections and restarting when the new release was deployed. That is why the collection was stopped.

The collection history did not get updated because the collections were not manually stopped from the UI. So all collections that were running on Thursday when the system was stopped for upgrade would have a missing entry from collection history

@collected tweets not being updated - yes that is an issue I noticed in your collection. Investigating why it wasnt being updated even though the collection status was "running" but no new tweets were being generated.

Collaborator

meghnas commented Aug 10, 2015

On Thursday, we had a new release of AIDR (v2.0), which required stopping all collections and restarting when the new release was deployed. That is why the collection was stopped.

The collection history did not get updated because the collections were not manually stopped from the UI. So all collections that were running on Thursday when the system was stopped for upgrade would have a missing entry from collection history

@collected tweets not being updated - yes that is an issue I noticed in your collection. Investigating why it wasnt being updated even though the collection status was "running" but no new tweets were being generated.

@meghnas

This comment has been minimized.

Show comment
Hide comment
@meghnas

meghnas Aug 10, 2015

Collaborator

For the same collection, when Ingmar tried to login to AIDR to restart the collection, the following error was received:

HTTP Status 401 - Authentication Failed: SpringSocialSecurity sign in details not found in session
type: Status report
message: Authentication Failed: SpringSocialSecurity sign in details not found in session
description: This request requires HTTP authentication.

Collaborator

meghnas commented Aug 10, 2015

For the same collection, when Ingmar tried to login to AIDR to restart the collection, the following error was received:

HTTP Status 401 - Authentication Failed: SpringSocialSecurity sign in details not found in session
type: Status report
message: Authentication Failed: SpringSocialSecurity sign in details not found in session
description: This request requires HTTP authentication.

@meghnas meghnas added the bug label Aug 10, 2015

@meghnas

This comment has been minimized.

Show comment
Hide comment
@meghnas

meghnas Aug 10, 2015

Collaborator

We found the reason for tweets not being updated - there was a thread pool issue in the glassfish server which caused the collections to stop working, and an issue in the code that did not update the status to "not running" and continued to display "running" status. The thread pool issue has now been resolved.
The next release of AIDR will address the code issue.

Collaborator

meghnas commented Aug 10, 2015

We found the reason for tweets not being updated - there was a thread pool issue in the glassfish server which caused the collections to stop working, and an issue in the code that did not update the status to "not running" and continued to display "running" status. The thread pool issue has now been resolved.
The next release of AIDR will address the code issue.

kushalkantgoyal added a commit that referenced this issue Jul 25, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment