[jira] [Created] (SOLR-3082) If you use a lazy replication request handler, the commit listener will not be registered right away, and might miss tracking the last commit.

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Created] (SOLR-3082) If you use a lazy replication request handler, the commit listener will not be registered right away, and might miss tracking the last commit.

Sebastian Nagel (Jira)
If you use a lazy replication request handler, the commit listener will not be registered right away, and might miss tracking the last commit.
----------------------------------------------------------------------------------------------------------------------------------------------

                 Key: SOLR-3082
                 URL: https://issues.apache.org/jira/browse/SOLR-3082
             Project: Solr
          Issue Type: Bug
            Reporter: Mark Miller
            Assignee: Mark Miller
             Fix For: 4.0


The result is that you might see version 0 as the latest commit version when it's really not.

--
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

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (SOLR-3082) If you use a lazy replication request handler, the commit listener will not be registered right away, and might miss tracking the last commit.

Sebastian Nagel (Jira)

    [ https://issues.apache.org/jira/browse/SOLR-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13197338#comment-13197338 ]

Mark Miller commented on SOLR-3082:
-----------------------------------

So I'm thinking: if you latest replacateable commit point is null and replicate on commit is on, we simply return the version/gen from the latest commit point.
               

> If you use a lazy replication request handler, the commit listener will not be registered right away, and might miss tracking the last commit.
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-3082
>                 URL: https://issues.apache.org/jira/browse/SOLR-3082
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>             Fix For: 4.0
>
>
> The result is that you might see version 0 as the latest commit version when it's really not.

--
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

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] [Issue Comment Edited] (SOLR-3082) If you use a lazy replication request handler, the commit listener will not be registered right away, and might miss tracking the last commit.

Sebastian Nagel (Jira)
In reply to this post by Sebastian Nagel (Jira)

    [ https://issues.apache.org/jira/browse/SOLR-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13197338#comment-13197338 ]

Mark Miller edited comment on SOLR-3082 at 1/31/12 10:40 PM:
-------------------------------------------------------------

So I'm thinking: if the latest replacateable commit point is null and replicate on commit is on, we simply return the version/gen from the latest commit point.
               
      was (Author: [hidden email]):
    So I'm thinking: if you latest replacateable commit point is null and replicate on commit is on, we simply return the version/gen from the latest commit point.
                 

> If you use a lazy replication request handler, the commit listener will not be registered right away, and might miss tracking the last commit.
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-3082
>                 URL: https://issues.apache.org/jira/browse/SOLR-3082
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>             Fix For: 4.0
>
>
> The result is that you might see version 0 as the latest commit version when it's really not.

--
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

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (SOLR-3082) If you use a lazy replication request handler, the commit listener will not be registered right away, and might miss tracking the last commit.

Sebastian Nagel (Jira)
In reply to this post by Sebastian Nagel (Jira)

    [ https://issues.apache.org/jira/browse/SOLR-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13197351#comment-13197351 ]

Mark Miller commented on SOLR-3082:
-----------------------------------

there is a sys out in there ill cleanup
               

> If you use a lazy replication request handler, the commit listener will not be registered right away, and might miss tracking the last commit.
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-3082
>                 URL: https://issues.apache.org/jira/browse/SOLR-3082
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>             Fix For: 4.0
>
>         Attachments: SOLR-3082.patch
>
>
> The result is that you might see version 0 as the latest commit version when it's really not.

--
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

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] [Updated] (SOLR-3082) If you use a lazy replication request handler, the commit listener will not be registered right away, and might miss tracking the last commit.

Sebastian Nagel (Jira)
In reply to this post by Sebastian Nagel (Jira)

     [ https://issues.apache.org/jira/browse/SOLR-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Miller updated SOLR-3082:
------------------------------

    Attachment: SOLR-3082.patch

simple patch
               

> If you use a lazy replication request handler, the commit listener will not be registered right away, and might miss tracking the last commit.
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-3082
>                 URL: https://issues.apache.org/jira/browse/SOLR-3082
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>             Fix For: 4.0
>
>         Attachments: SOLR-3082.patch
>
>
> The result is that you might see version 0 as the latest commit version when it's really not.

--
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

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (SOLR-3082) If you use a lazy replication request handler, the commit listener will not be registered right away, and might miss tracking the last commit.

Sebastian Nagel (Jira)
In reply to this post by Sebastian Nagel (Jira)

    [ https://issues.apache.org/jira/browse/SOLR-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199501#comment-13199501 ]

Mark Miller commented on SOLR-3082:
-----------------------------------

This does not really solve things for the replicate on optimize option, but it does deal with the replicate on commit option and in general offers better behavior I think - I'll commit this soon if there is no objection.
               

> If you use a lazy replication request handler, the commit listener will not be registered right away, and might miss tracking the last commit.
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-3082
>                 URL: https://issues.apache.org/jira/browse/SOLR-3082
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>             Fix For: 4.0
>
>         Attachments: SOLR-3082.patch
>
>
> The result is that you might see version 0 as the latest commit version when it's really not.

--
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

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] [Resolved] (SOLR-3082) If you use a lazy replication request handler, the commit listener will not be registered right away, and might miss tracking the last commit.

Sebastian Nagel (Jira)
In reply to this post by Sebastian Nagel (Jira)

     [ https://issues.apache.org/jira/browse/SOLR-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Miller resolved SOLR-3082.
-------------------------------

    Resolution: Fixed
   

> If you use a lazy replication request handler, the commit listener will not be registered right away, and might miss tracking the last commit.
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-3082
>                 URL: https://issues.apache.org/jira/browse/SOLR-3082
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>             Fix For: 4.0
>
>         Attachments: SOLR-3082.patch
>
>
> The result is that you might see version 0 as the latest commit version when it's really not.

--
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

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]