From dev-return-18866-archive-asf-public=cust-asf.ponee.io@manifoldcf.apache.org Tue Dec 11 08:44:09 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 63A51180671 for ; Tue, 11 Dec 2018 08:44:09 +0100 (CET) Received: (qmail 52655 invoked by uid 500); 11 Dec 2018 07:44:08 -0000 Mailing-List: contact dev-help@manifoldcf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@manifoldcf.apache.org Delivered-To: mailing list dev@manifoldcf.apache.org Received: (qmail 52640 invoked by uid 99); 11 Dec 2018 07:44:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2018 07:44:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id CB33DC58BF for ; Tue, 11 Dec 2018 07:44:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id vGrluP-FqjnZ for ; Tue, 11 Dec 2018 07:44:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 510A15F169 for ; Tue, 11 Dec 2018 07:34:17 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 77C40E0104 for ; Tue, 11 Dec 2018 07:34:16 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 43A95252F4 for ; Tue, 11 Dec 2018 07:34:00 +0000 (UTC) Date: Tue, 11 Dec 2018 07:34:00 +0000 (UTC) From: "Karl Wright (JIRA)" To: dev@manifoldcf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CONNECTORS-1562) Document removal Elastic MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CONNECTORS-1562?page=3Dcom.atla= ssian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId= =3D16716411#comment-16716411 ]=20 Karl Wright commented on CONNECTORS-1562: ----------------------------------------- I tried this out using a small number of the specific seeds provided. I st= arted with the following: {code} https://www.uantwerpen.be/en/ https://www.uantwerpen.be/en/about-uantwerp/ https://www.uantwerpen.be/en/about-uantwerp/about-uantwerp/ https://www.uantwerpen.be/en/about-uantwerp/catering-conventionhalls/ https://www.uantwerpen.be/en/about-uantwerp/catering-conventionhalls/conven= tion-halls/ https://www.uantwerpen.be/en/about-uantwerp/catering-conventionhalls/conven= tion-halls/hof-van-liere/ https://www.uantwerpen.be/en/about-uantwerp/catering-conventionhalls/univer= sity-club https://www.uantwerpen.be/en/about-uantwerp/facts-figures {code} This generated seven ingestions. I then more-or-less randomly removed a fe= w seeds, leaving this: {code} https://www.uantwerpen.be/en/ https://www.uantwerpen.be/en/about-uantwerp/ https://www.uantwerpen.be/en/about-uantwerp/about-uantwerp/ https://www.uantwerpen.be/en/about-uantwerp/catering-conventionhalls/univer= sity-club https://www.uantwerpen.be/en/about-uantwerp/facts-figures {code} Rerunning produced zero deletions, and a refetch of all seven previously-in= gested documents, with no new ingestions. Finally, I removed all the seeds and ran it again. A deletion was logged f= or every indexed document. My quick analysis of what is happening here is this: - ManifoldCF keeps grave markers around for hopcount tracking. Hopcount tr= acking in MCF is extremely complex and much care is taken to avoid miscalcu= lating the number of hops to a document, no matter what order documents are= processed in. In order to make that work, documents cannot be deleted fro= m the queue just because their hopcount is too large; instead, quite a numb= er of documents are put in the queue and may or may not be fetched, dependi= ng if they wind up with a low enough hopcount - The document deletion phase removes unreachable documents, but documents = that simply have too great a hopcount but otherwise are in the queue are no= t precisely unreachable In other words, the cleanup phase of a job seems to interact badly with doc= uments that are reachable but just have too great a hopcount; these documen= ts seem to be overlooked for cleanup, and will ONLY be cleaned up when they= become truly unreachable. This is not intended behavior. However, it's also a behavior change in a v= ery complex part of the software, and will therefore require great care to = correct without breaking something. Because it is not something simple, yo= u should expect me to require a couple of weeks elapsed time to come up wit= h the right fix. Furthermore, it is still true that this model is not one that I'd recommend= for crawling a web site. The web connector is not designed to operate wit= h hundreds of thousands of seeds; hundreds, maybe, or thousands on a bad da= y, but trying to control exactly what MCF indexes by fooling with the seed = list is not what it was designed for. > Document removal Elastic > ------------------------ > > Key: CONNECTORS-1562 > URL: https://issues.apache.org/jira/browse/CONNECTORS-156= 2 > Project: ManifoldCF > Issue Type: Bug > Components: Elastic Search connector, Web connector > Affects Versions: ManifoldCF 2.11 > Environment: Manifoldcf 2.11 > Elasticsearch=C2=A06.3.2 > Web inputconnector > elastic outputconnecotr > Job crawls website input and outputs content to elastic > Reporter: Tim Steenbeke > Assignee: Karl Wright > Priority: Critical > Labels: starter > Attachments: 30URLSeeds.png, 3URLSeed.png, Screenshot from 2018-1= 2-10 14-07-46.png > > Original Estimate: 4h > Remaining Estimate: 4h > > My documents aren't removed from ElasticSearch index after rerunning the = changed seeds > I update my job to change the seedmap and rerun it or use the schedualer = to keep it runneng even after updating it. > After the rerun the unreachable documents don't get deleted. > It only adds doucments when they can be reached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)