[jira] [Created] (CONNECTORS-279) Postgresql load test job delete document cleanup fails sometimes and leaves orphaned documents
Postgresql load test job delete document cleanup fails sometimes and leaves orphaned documents -- Key: CONNECTORS-279 URL: https://issues.apache.org/jira/browse/CONNECTORS-279 Project: ManifoldCF Issue Type: Bug Components: Framework crawler agent Affects Versions: ManifoldCF 0.4 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.4 Running the postgresql load test on my laptop, I was surprised when the test did not finish. The UI indicated that the job was being deleted, but there were 49,000 documents and that number was not moving. Further inspection yielded the following: - Job was in the DELETING state - Documents were in the BEINGDELETED state - No activity of any kind ongoing The log had no errors. It was impossible to get a thread dump, but a cursory inspection of the code indicated that either the documents were being marked as BEINGDELETED but were not actually being placed on the in-memory queue, or the delete threads were picking up the documents and somehow avoiding marking them as being processed. Also, probably unrelated, the Document Status report listed these documents as having a status of Being removed and a state of Unknown. The Unknown should have been a Deleting. Since the extended WHEN... ELSE clause has a reasonable condition for the Deleting answer, it's hard to see how this could have occurred either. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-277) WikiConnector - option to limit crawl by namespace
[ https://issues.apache.org/jira/browse/CONNECTORS-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13132500#comment-13132500 ] Tobias Wunderlich commented on CONNECTORS-277: -- Changes to namespace and title are not applied to the job coorectly. Altough the changes are displayed after clicking save, they don't show up reediting the job. WikiConnector - option to limit crawl by namespace -- Key: CONNECTORS-277 URL: https://issues.apache.org/jira/browse/CONNECTORS-277 Project: ManifoldCF Issue Type: Improvement Components: Wiki connector Affects Versions: ManifoldCF 0.4 Reporter: Tobias Wunderlich Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 0.4 At the moment, the WikiConnector crawls the whole Wiki. This can take up a lot of time. For testing purposes an option to limit the pages to crawl by namespaces(title) would be great. Tobias -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CONNECTORS-280) When job deletion has started, but job is not yet deleting documents, Not yet run is displayed on status page
[ https://issues.apache.org/jira/browse/CONNECTORS-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-280: -- Assignee: Karl Wright When job deletion has started, but job is not yet deleting documents, Not yet run is displayed on status page --- Key: CONNECTORS-280 URL: https://issues.apache.org/jira/browse/CONNECTORS-280 Project: ManifoldCF Issue Type: Bug Components: Framework crawler agent Affects Versions: ManifoldCF 0.4 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.4 Not yet run is displayed but the correct status should be something else. The job's status value is V, which corresponds to state DELETESTARTINGUP. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-280) When job deletion has started, but job is not yet deleting documents, Not yet run is displayed on status page
[ https://issues.apache.org/jira/browse/CONNECTORS-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-280. Resolution: Fixed r1187210. When job deletion has started, but job is not yet deleting documents, Not yet run is displayed on status page --- Key: CONNECTORS-280 URL: https://issues.apache.org/jira/browse/CONNECTORS-280 Project: ManifoldCF Issue Type: Bug Components: Framework crawler agent Affects Versions: ManifoldCF 0.4 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.4 Not yet run is displayed but the correct status should be something else. The job's status value is V, which corresponds to state DELETESTARTINGUP. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-277) WikiConnector - option to limit crawl by namespace
[ https://issues.apache.org/jira/browse/CONNECTORS-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13132524#comment-13132524 ] Karl Wright commented on CONNECTORS-277: r1187220 to correct this latest issue. WikiConnector - option to limit crawl by namespace -- Key: CONNECTORS-277 URL: https://issues.apache.org/jira/browse/CONNECTORS-277 Project: ManifoldCF Issue Type: Improvement Components: Wiki connector Affects Versions: ManifoldCF 0.4 Reporter: Tobias Wunderlich Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 0.4 At the moment, the WikiConnector crawls the whole Wiki. This can take up a lot of time. For testing purposes an option to limit the pages to crawl by namespaces(title) would be great. Tobias -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
