You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Yonik Seeley (JIRA)" <ji...@apache.org> on 2009/09/28 03:42:16 UTC

[jira] Created: (SOLR-1469) TestReplicationHandler failure

TestReplicationHandler failure
------------------------------

                 Key: SOLR-1469
                 URL: https://issues.apache.org/jira/browse/SOLR-1469
             Project: Solr
          Issue Type: Bug
            Reporter: Yonik Seeley


TestReplicationHandler seems to fail often.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (SOLR-1469) TestReplicationHandler failure

Posted by "Yonik Seeley (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SOLR-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12760236#action_12760236 ] 

Yonik Seeley commented on SOLR-1469:
------------------------------------

I just committed the fix for the assertion failure above. 
The failures left now are due to connection refused exceptions.

> TestReplicationHandler failure
> ------------------------------
>
>                 Key: SOLR-1469
>                 URL: https://issues.apache.org/jira/browse/SOLR-1469
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Yonik Seeley
>         Attachments: TestReplicationHandler.FAILED.210743
>
>
> TestReplicationHandler seems to fail often.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (SOLR-1469) TestReplicationHandler failure

Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SOLR-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12760134#action_12760134 ] 

Mark Miller commented on SOLR-1469:
-----------------------------------

Are you using Windows? Havn't gotten it to fail on Linux yet.

Perhaps we should add a check of the status returned from index in there?

> TestReplicationHandler failure
> ------------------------------
>
>                 Key: SOLR-1469
>                 URL: https://issues.apache.org/jira/browse/SOLR-1469
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Yonik Seeley
>         Attachments: TestReplicationHandler.FAILED.210743
>
>
> TestReplicationHandler seems to fail often.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (SOLR-1469) TestReplicationHandler failure

Posted by "Yonik Seeley (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SOLR-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yonik Seeley updated SOLR-1469:
-------------------------------

    Attachment: TestReplicationHandler.FAILED.210743

Attaching one particular worrying failure.

Testcase: testReplicateAfterWrite2Slave took 2.656 sec
        FAILED
expected:<1> but was:<0>
junit.framework.AssertionFailedError: expected:<1> but was:<0>
        at org.apache.solr.handler.TestReplicationHandler.testReplicateAfterWrite2Slave(TestReplicationHandler.java:424)

So replication was disabled, a doc was added to the slave, but then the search for it failed.  How can that be?

> TestReplicationHandler failure
> ------------------------------
>
>                 Key: SOLR-1469
>                 URL: https://issues.apache.org/jira/browse/SOLR-1469
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Yonik Seeley
>         Attachments: TestReplicationHandler.FAILED.210743
>
>
> TestReplicationHandler seems to fail often.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (SOLR-1469) TestReplicationHandler failure

Posted by "Yonik Seeley (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SOLR-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761947#action_12761947 ] 

Yonik Seeley commented on SOLR-1469:
------------------------------------

Jetty still fails to come up occasionally, even after waiting 2 minutes.  I also tested with the latest Jetty 6.1.21 - same results.
At this point, it could still be a Solr bug or a Jetty bug.

> TestReplicationHandler failure
> ------------------------------
>
>                 Key: SOLR-1469
>                 URL: https://issues.apache.org/jira/browse/SOLR-1469
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Yonik Seeley
>         Attachments: TestReplicationHandler.FAILED.210743
>
>
> TestReplicationHandler seems to fail often.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (SOLR-1469) TestReplicationHandler failure

Posted by "Yonik Seeley (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SOLR-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12760146#action_12760146 ] 

Yonik Seeley commented on SOLR-1469:
------------------------------------

OK, I think this particular one might be a bug in the test.
Replication is disabled only after the master commit - and in the test log provided it looks like the start of a replication sneeks in there, and finishes after the addDoc() on the slave.

I'll leave the tests running in a loop tonight and see if moving the disableReplication before the master commit fixes things.

> TestReplicationHandler failure
> ------------------------------
>
>                 Key: SOLR-1469
>                 URL: https://issues.apache.org/jira/browse/SOLR-1469
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Yonik Seeley
>         Attachments: TestReplicationHandler.FAILED.210743
>
>
> TestReplicationHandler seems to fail often.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.