You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Neha Narkhede (JIRA)" <ji...@apache.org> on 2012/06/01 00:41:23 UTC

[jira] [Created] (KAFKA-355) Move high watermark maintenance logic out of Log

Neha Narkhede created KAFKA-355:
-----------------------------------

             Summary: Move high watermark maintenance logic out of Log
                 Key: KAFKA-355
                 URL: https://issues.apache.org/jira/browse/KAFKA-355
             Project: Kafka
          Issue Type: Sub-task
            Reporter: Neha Narkhede


Jay had a good suggestion as part of the review for KAFKA-46 -

Maybe HW mark should move out of Log since now it really indicates something about the state of other servers and Log is meant to be just a simple stand alone log implementation.

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

        

[jira] [Assigned] (KAFKA-355) Move high watermark maintenance logic out of Log

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

Neha Narkhede reassigned KAFKA-355:
-----------------------------------

    Assignee: Neha Narkhede
    
> Move high watermark maintenance logic out of Log
> ------------------------------------------------
>
>                 Key: KAFKA-355
>                 URL: https://issues.apache.org/jira/browse/KAFKA-355
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Neha Narkhede
>            Assignee: Neha Narkhede
>
> Jay had a good suggestion as part of the review for KAFKA-46 -
> Maybe HW mark should move out of Log since now it really indicates something about the state of other servers and Log is meant to be just a simple stand alone log implementation.

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

        

[jira] [Resolved] (KAFKA-355) Move high watermark maintenance logic out of Log

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

Neha Narkhede resolved KAFKA-355.
---------------------------------

    Resolution: Fixed

Fixed as part of KAFKA-405
                
> Move high watermark maintenance logic out of Log
> ------------------------------------------------
>
>                 Key: KAFKA-355
>                 URL: https://issues.apache.org/jira/browse/KAFKA-355
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Neha Narkhede
>            Assignee: Neha Narkhede
>
> Jay had a good suggestion as part of the review for KAFKA-46 -
> Maybe HW mark should move out of Log since now it really indicates something about the state of other servers and Log is meant to be just a simple stand alone log implementation.

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