From dev-return-313944-archive-asf-public=cust-asf.ponee.io@lucene.apache.org Tue Mar 6 18:06:04 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 6E41F180652 for ; Tue, 6 Mar 2018 18:06:04 +0100 (CET) Received: (qmail 49835 invoked by uid 500); 6 Mar 2018 17:06:03 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 49706 invoked by uid 99); 6 Mar 2018 17:06:02 -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, 06 Mar 2018 17:06:02 +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 8B5DFC6905 for ; Tue, 6 Mar 2018 17:06:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.31 X-Spam-Level: X-Spam-Status: No, score=-110.31 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100, WEIRD_PORT=0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id e2O7S70ZVqe2 for ; Tue, 6 Mar 2018 17:06:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 557C15F588 for ; Tue, 6 Mar 2018 17:06:01 +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 A0C79E024F for ; Tue, 6 Mar 2018 17:06:00 +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 4CAB721279 for ; Tue, 6 Mar 2018 17:06:00 +0000 (UTC) Date: Tue, 6 Mar 2018 17:06:00 +0000 (UTC) From: "Amrit Sarkar (JIRA)" To: dev@lucene.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (SOLR-12057) CDCR does not replicate to Collections with TLOG Replicas 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/SOLR-12057?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] Amrit Sarkar updated SOLR-12057: -------------------------------- Attachment: cdcr-fail-with-tlog-pull.patch > CDCR does not replicate to Collections with TLOG Replicas > --------------------------------------------------------- > > Key: SOLR-12057 > URL: https://issues.apache.org/jira/browse/SOLR-12057 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public)=20 > Components: CDCR > Affects Versions: 7.2 > Reporter: Webster Homer > Priority: Major > Attachments: cdcr-fail-with-tlog-pull.patch, cdcr-fail-with-tlog-= pull.patch > > > We created a collection using TLOG replicas in our QA clouds. > We have a locally hosted solrcloud with 2 nodes, all our collections have= 2 shards. We use CDCR to replicate the collections from this environment t= o 2 data centers hosted in Google cloud. This seems to work fairly well for= our collections with NRT replicas. However the new TLOG collection has pro= blems. > =C2=A0 > The google cloud solrclusters have 4 nodes each (3 separate Zookeepers). = 2 shards per collection with 2 replicas per shard. > =C2=A0 > We never see data show up in the cloud collections, but we do see tlog fi= les show up on the cloud servers. I can see that all of the servers have cd= cr started, buffers are disabled. > The cdcr source configuration is: > =C2=A0 > "requestHandler":{"/cdcr":{ > =C2=A0 =C2=A0 =C2=A0 "name":"/cdcr", > =C2=A0 =C2=A0 =C2=A0 "class":"solr.CdcrRequestHandler", > =C2=A0 =C2=A0 =C2=A0 "replica":[ > =C2=A0 =C2=A0 =C2=A0 =C2=A0 { > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 "zkHost":"[xxx-mzk01.sial.com:2181|htt= p://xxx-mzk01.sial.com:2181/],[xxx-mzk02.sial.com:2181|http://xxx-mzk02.sia= l.com:2181/],[xxx-mzk03.sial.com:2181/solr|http://xxx-mzk03.sial.com:2181/s= olr]", > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 "source":"b2b-catalog-material-180124T= ", > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 "target":"b2b-catalog-material-180124T= "}, > =C2=A0 =C2=A0 =C2=A0 =C2=A0 { > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 "zkHost":"[yyyy-mzk01.sial.com:2181|ht= tp://yyyy-mzk01.sial.com:2181/],[yyyy-mzk02.sial.com:2181|http://yyyy-mzk02= .sial.com:2181/],[yyyy-mzk03.sial.com:2181/solr|http://yyyy-mzk03.sial.com:= 2181/solr]", > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 "source":"b2b-catalog-material-180124T= ", > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 "target":"b2b-catalog-material-180124T= "}], > =C2=A0 =C2=A0 =C2=A0 "replicator":{ > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "threadPoolSize":4, > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "schedule":500, > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "batchSize":250}, > =C2=A0 =C2=A0 =C2=A0 "updateLogSynchronizer":\{"schedule":60000}}}} > =C2=A0 > The target configurations in the 2 clouds are the same: > "requestHandler":{"/cdcr":{ "name":"/cdcr", "class":"solr.CdcrRequestHand= ler", "buffer":{"defaultState":"disabled"}}}=C2=A0 > =C2=A0 > All of our collections have a timestamp field, index_date. In the source = collection all the records have a date of 2/28/2018 but the target collecti= ons have a latest date of 1/26/2018 > =C2=A0 > I don't see cdcr errors in the logs, but we use logstash to search them, = and we're still perfecting that.=C2=A0 > =C2=A0 > We have a number of similar collections that behave correctly. This is th= e only collection that is a TLOG collection. It appears that CDCR doesn't s= upport TLOG collections. > =C2=A0 > It looks like the data is getting to the target servers. I see tlog files= with the right timestamps. Looking at the timestamps on the documents in t= he collection none of the data appears to have been loaded.In the solr.log = I see lots of /cdcr messages=C2=A0=C2=A0action=3DLASTPROCESSEDVERSION, =C2= =A0action=3DCOLLECTIONCHECKPOINT, and =C2=A0action=3DSHARDCHECKPOINT=C2=A0 > =C2=A0 > no errors > =C2=A0 > Target collections autoCommit is set to=C2=A0 60000 I tried sending a com= mit explicitly no difference. cdcr is uploading data, but no new data appea= rs in the collection. > =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org