[jira] [Commented] (SOLR-9036) Solr slave is doing full replication (entire index) of index after master restart
[ https://issues.apache.org/jira/browse/SOLR-9036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15544167#comment-15544167 ] Shalin Shekhar Mangar commented on SOLR-9036: - I don't see how it would. This bug affected master-slave (non-solr cloud) replication only. > Solr slave is doing full replication (entire index) of index after master > restart > - > > Key: SOLR-9036 > URL: https://issues.apache.org/jira/browse/SOLR-9036 > Project: Solr > Issue Type: Bug > Components: replication (java) >Affects Versions: 5.3.1, 6.0 >Reporter: Shalin Shekhar Mangar >Assignee: Shalin Shekhar Mangar >Priority: Critical > Labels: impact-high > Fix For: 5.5.2, 5.6, 6.0.1, 6.1, master (7.0) > > Attachments: SOLR-9036.patch, SOLR-9036.patch, SOLR-9036.patch > > > This was first described in the following email: > https://mail-archives.apache.org/mod_mbox/lucene-solr-user/201604.mbox/%3ccafgnfoyn+xmpxwzwbjuzddeuz7tjqhqktek6q7u8xgstqy3...@mail.gmail.com%3E > I tried Solr 5.3.1 and Solr 6 and I can reproduce the problem. If the master > comes back online before the next polling interval then the slave finds > itself in sync with the master but if the master is down for at least one > polling interval then the slave pulls the entire full index from the master > even if the index has not changed on the master. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9036) Solr slave is doing full replication (entire index) of index after master restart
[ https://issues.apache.org/jira/browse/SOLR-9036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15544142#comment-15544142 ] Pushkar Raste commented on SOLR-9036: - Does fix for [SOLR-9446|https://issues.apache.org/jira/browse/SOLR-9446] helps in this situation? > Solr slave is doing full replication (entire index) of index after master > restart > - > > Key: SOLR-9036 > URL: https://issues.apache.org/jira/browse/SOLR-9036 > Project: Solr > Issue Type: Bug > Components: replication (java) >Affects Versions: 5.3.1, 6.0 >Reporter: Shalin Shekhar Mangar >Assignee: Shalin Shekhar Mangar >Priority: Critical > Labels: impact-high > Fix For: 5.5.2, 5.6, 6.0.1, 6.1, master (7.0) > > Attachments: SOLR-9036.patch, SOLR-9036.patch, SOLR-9036.patch > > > This was first described in the following email: > https://mail-archives.apache.org/mod_mbox/lucene-solr-user/201604.mbox/%3ccafgnfoyn+xmpxwzwbjuzddeuz7tjqhqktek6q7u8xgstqy3...@mail.gmail.com%3E > I tried Solr 5.3.1 and Solr 6 and I can reproduce the problem. If the master > comes back online before the next polling interval then the slave finds > itself in sync with the master but if the master is down for at least one > polling interval then the slave pulls the entire full index from the master > even if the index has not changed on the master. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9036) Solr slave is doing full replication (entire index) of index after master restart
[ https://issues.apache.org/jira/browse/SOLR-9036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15539623#comment-15539623 ] Alexandre Rafalovitch commented on SOLR-9036: - The work here seems to be all done. Safe to close? > Solr slave is doing full replication (entire index) of index after master > restart > - > > Key: SOLR-9036 > URL: https://issues.apache.org/jira/browse/SOLR-9036 > Project: Solr > Issue Type: Bug > Components: replication (java) >Affects Versions: 5.3.1, 6.0 >Reporter: Shalin Shekhar Mangar >Assignee: Shalin Shekhar Mangar >Priority: Critical > Labels: impact-high > Fix For: 5.5.2, 5.6, 6.0.1, 6.1, master (7.0) > > Attachments: SOLR-9036.patch, SOLR-9036.patch, SOLR-9036.patch > > > This was first described in the following email: > https://mail-archives.apache.org/mod_mbox/lucene-solr-user/201604.mbox/%3ccafgnfoyn+xmpxwzwbjuzddeuz7tjqhqktek6q7u8xgstqy3...@mail.gmail.com%3E > I tried Solr 5.3.1 and Solr 6 and I can reproduce the problem. If the master > comes back online before the next polling interval then the slave finds > itself in sync with the master but if the master is down for at least one > polling interval then the slave pulls the entire full index from the master > even if the index has not changed on the master. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9036) Solr slave is doing full replication (entire index) of index after master restart
[ https://issues.apache.org/jira/browse/SOLR-9036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15336958#comment-15336958 ] ASF subversion and git services commented on SOLR-9036: --- Commit 669b9cd00378cf14279ba81563b33807d3b68624 in lucene-solr's branch refs/heads/branch_5_5 from [~shalinmangar] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=669b9cd ] SOLR-9036: Solr slave is doing full replication (entire index) of index after master restart (cherry picked from commit 51b1319) > Solr slave is doing full replication (entire index) of index after master > restart > - > > Key: SOLR-9036 > URL: https://issues.apache.org/jira/browse/SOLR-9036 > Project: Solr > Issue Type: Bug > Components: replication (java) >Affects Versions: 5.3.1, 6.0 >Reporter: Shalin Shekhar Mangar >Assignee: Shalin Shekhar Mangar >Priority: Critical > Labels: impact-high > Fix For: 5.6, 6.0.1, 6.1, 5.5.2, master (7.0) > > Attachments: SOLR-9036.patch, SOLR-9036.patch, SOLR-9036.patch > > > This was first described in the following email: > https://mail-archives.apache.org/mod_mbox/lucene-solr-user/201604.mbox/%3ccafgnfoyn+xmpxwzwbjuzddeuz7tjqhqktek6q7u8xgstqy3...@mail.gmail.com%3E > I tried Solr 5.3.1 and Solr 6 and I can reproduce the problem. If the master > comes back online before the next polling interval then the slave finds > itself in sync with the master but if the master is down for at least one > polling interval then the slave pulls the entire full index from the master > even if the index has not changed on the master. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9036) Solr slave is doing full replication (entire index) of index after master restart
[ https://issues.apache.org/jira/browse/SOLR-9036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15336960#comment-15336960 ] ASF subversion and git services commented on SOLR-9036: --- Commit 912c3da3eb7fa6d84b38357cd77c9727a24ef598 in lucene-solr's branch refs/heads/branch_5x from [~shalinmangar] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=912c3da ] SOLR-9036: Solr slave is doing full replication (entire index) of index after master restart (cherry picked from commit 51b1319) > Solr slave is doing full replication (entire index) of index after master > restart > - > > Key: SOLR-9036 > URL: https://issues.apache.org/jira/browse/SOLR-9036 > Project: Solr > Issue Type: Bug > Components: replication (java) >Affects Versions: 5.3.1, 6.0 >Reporter: Shalin Shekhar Mangar >Assignee: Shalin Shekhar Mangar >Priority: Critical > Labels: impact-high > Fix For: 5.6, 6.0.1, 6.1, 5.5.2, master (7.0) > > Attachments: SOLR-9036.patch, SOLR-9036.patch, SOLR-9036.patch > > > This was first described in the following email: > https://mail-archives.apache.org/mod_mbox/lucene-solr-user/201604.mbox/%3ccafgnfoyn+xmpxwzwbjuzddeuz7tjqhqktek6q7u8xgstqy3...@mail.gmail.com%3E > I tried Solr 5.3.1 and Solr 6 and I can reproduce the problem. If the master > comes back online before the next polling interval then the slave finds > itself in sync with the master but if the master is down for at least one > polling interval then the slave pulls the entire full index from the master > even if the index has not changed on the master. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9036) Solr slave is doing full replication (entire index) of index after master restart
[ https://issues.apache.org/jira/browse/SOLR-9036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15336954#comment-15336954 ] Steve Rowe commented on SOLR-9036: -- Backporting to 5.6 and 5.5.2. > Solr slave is doing full replication (entire index) of index after master > restart > - > > Key: SOLR-9036 > URL: https://issues.apache.org/jira/browse/SOLR-9036 > Project: Solr > Issue Type: Bug > Components: replication (java) >Affects Versions: 5.3.1, 6.0 >Reporter: Shalin Shekhar Mangar >Assignee: Shalin Shekhar Mangar >Priority: Critical > Labels: impact-high > Fix For: 6.0.1, 6.1, master (7.0) > > Attachments: SOLR-9036.patch, SOLR-9036.patch, SOLR-9036.patch > > > This was first described in the following email: > https://mail-archives.apache.org/mod_mbox/lucene-solr-user/201604.mbox/%3ccafgnfoyn+xmpxwzwbjuzddeuz7tjqhqktek6q7u8xgstqy3...@mail.gmail.com%3E > I tried Solr 5.3.1 and Solr 6 and I can reproduce the problem. If the master > comes back online before the next polling interval then the slave finds > itself in sync with the master but if the master is down for at least one > polling interval then the slave pulls the entire full index from the master > even if the index has not changed on the master. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9036) Solr slave is doing full replication (entire index) of index after master restart
[ https://issues.apache.org/jira/browse/SOLR-9036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294287#comment-15294287 ] ASF subversion and git services commented on SOLR-9036: --- Commit 93a33e0892e2ad3c8f73755d4ba10da72ff9c11a in lucene-solr's branch refs/heads/branch_6_0 from [~shalinmangar] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=93a33e0 ] SOLR-9036: Solr slave is doing full replication (entire index) of index after master restart (cherry picked from commit 51b1319) > Solr slave is doing full replication (entire index) of index after master > restart > - > > Key: SOLR-9036 > URL: https://issues.apache.org/jira/browse/SOLR-9036 > Project: Solr > Issue Type: Bug > Components: replication (java) >Affects Versions: 5.3.1, 6.0 >Reporter: Shalin Shekhar Mangar >Assignee: Shalin Shekhar Mangar >Priority: Critical > Labels: impact-high > Fix For: 6.0.1, 6.1 > > Attachments: SOLR-9036.patch, SOLR-9036.patch, SOLR-9036.patch > > > This was first described in the following email: > https://mail-archives.apache.org/mod_mbox/lucene-solr-user/201604.mbox/%3ccafgnfoyn+xmpxwzwbjuzddeuz7tjqhqktek6q7u8xgstqy3...@mail.gmail.com%3E > I tried Solr 5.3.1 and Solr 6 and I can reproduce the problem. If the master > comes back online before the next polling interval then the slave finds > itself in sync with the master but if the master is down for at least one > polling interval then the slave pulls the entire full index from the master > even if the index has not changed on the master. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9036) Solr slave is doing full replication (entire index) of index after master restart
[ https://issues.apache.org/jira/browse/SOLR-9036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15273079#comment-15273079 ] ASF subversion and git services commented on SOLR-9036: --- Commit a6f9c8e171b8f48d5ced9c74b41f875aef567634 in lucene-solr's branch refs/heads/branch_6x from [~shalinmangar] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=a6f9c8e ] SOLR-9036: Disable doTestIndexFetchOnMasterRestart (cherry picked from commit 1dd8775) > Solr slave is doing full replication (entire index) of index after master > restart > - > > Key: SOLR-9036 > URL: https://issues.apache.org/jira/browse/SOLR-9036 > Project: Solr > Issue Type: Bug > Components: replication (java) >Affects Versions: 5.3.1, 6.0 >Reporter: Shalin Shekhar Mangar >Assignee: Shalin Shekhar Mangar >Priority: Critical > Labels: impact-high > Fix For: 6.1, master > > Attachments: SOLR-9036.patch, SOLR-9036.patch, SOLR-9036.patch > > > This was first described in the following email: > https://mail-archives.apache.org/mod_mbox/lucene-solr-user/201604.mbox/%3ccafgnfoyn+xmpxwzwbjuzddeuz7tjqhqktek6q7u8xgstqy3...@mail.gmail.com%3E > I tried Solr 5.3.1 and Solr 6 and I can reproduce the problem. If the master > comes back online before the next polling interval then the slave finds > itself in sync with the master but if the master is down for at least one > polling interval then the slave pulls the entire full index from the master > even if the index has not changed on the master. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9036) Solr slave is doing full replication (entire index) of index after master restart
[ https://issues.apache.org/jira/browse/SOLR-9036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15273077#comment-15273077 ] ASF subversion and git services commented on SOLR-9036: --- Commit 1dd877545fad0eae7be43fec109bceb4617fb6a4 in lucene-solr's branch refs/heads/master from [~shalinmangar] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=1dd8775 ] SOLR-9036: Disable doTestIndexFetchOnMasterRestart > Solr slave is doing full replication (entire index) of index after master > restart > - > > Key: SOLR-9036 > URL: https://issues.apache.org/jira/browse/SOLR-9036 > Project: Solr > Issue Type: Bug > Components: replication (java) >Affects Versions: 5.3.1, 6.0 >Reporter: Shalin Shekhar Mangar >Assignee: Shalin Shekhar Mangar >Priority: Critical > Labels: impact-high > Fix For: 6.1, master > > Attachments: SOLR-9036.patch, SOLR-9036.patch, SOLR-9036.patch > > > This was first described in the following email: > https://mail-archives.apache.org/mod_mbox/lucene-solr-user/201604.mbox/%3ccafgnfoyn+xmpxwzwbjuzddeuz7tjqhqktek6q7u8xgstqy3...@mail.gmail.com%3E > I tried Solr 5.3.1 and Solr 6 and I can reproduce the problem. If the master > comes back online before the next polling interval then the slave finds > itself in sync with the master but if the master is down for at least one > polling interval then the slave pulls the entire full index from the master > even if the index has not changed on the master. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9036) Solr slave is doing full replication (entire index) of index after master restart
[ https://issues.apache.org/jira/browse/SOLR-9036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15272512#comment-15272512 ] ASF subversion and git services commented on SOLR-9036: --- Commit 51b131950de0357fc64e0e951b887eb30a704cd1 in lucene-solr's branch refs/heads/master from [~shalinmangar] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=51b1319 ] SOLR-9036: Solr slave is doing full replication (entire index) of index after master restart > Solr slave is doing full replication (entire index) of index after master > restart > - > > Key: SOLR-9036 > URL: https://issues.apache.org/jira/browse/SOLR-9036 > Project: Solr > Issue Type: Bug > Components: replication (java) >Affects Versions: 5.3.1, 6.0 >Reporter: Shalin Shekhar Mangar >Priority: Critical > Labels: impact-high > Fix For: 6.1, master > > Attachments: SOLR-9036.patch, SOLR-9036.patch, SOLR-9036.patch > > > This was first described in the following email: > https://mail-archives.apache.org/mod_mbox/lucene-solr-user/201604.mbox/%3ccafgnfoyn+xmpxwzwbjuzddeuz7tjqhqktek6q7u8xgstqy3...@mail.gmail.com%3E > I tried Solr 5.3.1 and Solr 6 and I can reproduce the problem. If the master > comes back online before the next polling interval then the slave finds > itself in sync with the master but if the master is down for at least one > polling interval then the slave pulls the entire full index from the master > even if the index has not changed on the master. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9036) Solr slave is doing full replication (entire index) of index after master restart
[ https://issues.apache.org/jira/browse/SOLR-9036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15272514#comment-15272514 ] ASF subversion and git services commented on SOLR-9036: --- Commit 855d57bf10cc69037135242dd9911579b2046e84 in lucene-solr's branch refs/heads/branch_6x from [~shalinmangar] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=855d57b ] SOLR-9036: Solr slave is doing full replication (entire index) of index after master restart (cherry picked from commit 51b1319) > Solr slave is doing full replication (entire index) of index after master > restart > - > > Key: SOLR-9036 > URL: https://issues.apache.org/jira/browse/SOLR-9036 > Project: Solr > Issue Type: Bug > Components: replication (java) >Affects Versions: 5.3.1, 6.0 >Reporter: Shalin Shekhar Mangar >Priority: Critical > Labels: impact-high > Fix For: 6.1, master > > Attachments: SOLR-9036.patch, SOLR-9036.patch, SOLR-9036.patch > > > This was first described in the following email: > https://mail-archives.apache.org/mod_mbox/lucene-solr-user/201604.mbox/%3ccafgnfoyn+xmpxwzwbjuzddeuz7tjqhqktek6q7u8xgstqy3...@mail.gmail.com%3E > I tried Solr 5.3.1 and Solr 6 and I can reproduce the problem. If the master > comes back online before the next polling interval then the slave finds > itself in sync with the master but if the master is down for at least one > polling interval then the slave pulls the entire full index from the master > even if the index has not changed on the master. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9036) Solr slave is doing full replication (entire index) of index after master restart
[ https://issues.apache.org/jira/browse/SOLR-9036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15272470#comment-15272470 ] Mark Miller commented on SOLR-9036: --- Might be nice to add a little test, but +1 on patch. > Solr slave is doing full replication (entire index) of index after master > restart > - > > Key: SOLR-9036 > URL: https://issues.apache.org/jira/browse/SOLR-9036 > Project: Solr > Issue Type: Bug > Components: replication (java) >Affects Versions: 5.3.1, 6.0 >Reporter: Shalin Shekhar Mangar >Priority: Critical > Labels: impact-high > Fix For: 6.1, master > > Attachments: SOLR-9036.patch > > > This was first described in the following email: > https://mail-archives.apache.org/mod_mbox/lucene-solr-user/201604.mbox/%3ccafgnfoyn+xmpxwzwbjuzddeuz7tjqhqktek6q7u8xgstqy3...@mail.gmail.com%3E > I tried Solr 5.3.1 and Solr 6 and I can reproduce the problem. If the master > comes back online before the next polling interval then the slave finds > itself in sync with the master but if the master is down for at least one > polling interval then the slave pulls the entire full index from the master > even if the index has not changed on the master. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9036) Solr slave is doing full replication (entire index) of index after master restart
[ https://issues.apache.org/jira/browse/SOLR-9036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15257032#comment-15257032 ] Shalin Shekhar Mangar commented on SOLR-9036: - This was caused by SOLR-7134 where any previous replication failure forces a full replication regardless of whether we are in SolrCloud mode or the cause of the last failure. > Solr slave is doing full replication (entire index) of index after master > restart > - > > Key: SOLR-9036 > URL: https://issues.apache.org/jira/browse/SOLR-9036 > Project: Solr > Issue Type: Bug > Components: replication (java) >Affects Versions: 5.3.1, 6.0 >Reporter: Shalin Shekhar Mangar >Priority: Critical > Labels: impact-high > Fix For: master, 6.1 > > > This was first described in the following email: > https://mail-archives.apache.org/mod_mbox/lucene-solr-user/201604.mbox/%3ccafgnfoyn+xmpxwzwbjuzddeuz7tjqhqktek6q7u8xgstqy3...@mail.gmail.com%3E > I tried Solr 5.3.1 and Solr 6 and I can reproduce the problem. If the master > comes back online before the next polling interval then the slave finds > itself in sync with the master but if the master is down for at least one > polling interval then the slave pulls the entire full index from the master > even if the index has not changed on the master. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
