You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Robbie Scott (JIRA)" <ji...@apache.org> on 2008/10/06 16:05:44 UTC

[jira] Created: (ZOOKEEPER-161) Content needed: "Designing a ZooKeeper Deployment"

Content needed: "Designing a ZooKeeper Deployment"
--------------------------------------------------

                 Key: ZOOKEEPER-161
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-161
             Project: Zookeeper
          Issue Type: Sub-task
          Components: documentation
            Reporter: Robbie Scott


We should document how ops engineer should design their ZooKeeper deployments.  

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


[jira] Updated: (ZOOKEEPER-161) Content needed: "Designing a ZooKeeper Deployment"

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

Robbie Scott updated ZOOKEEPER-161:
-----------------------------------

        Fix Version/s: 3.0.1
    Affects Version/s: 3.0.1
               Status: Patch Available  (was: Open)

See attached diff as Patch fle

> Content needed: "Designing a ZooKeeper Deployment"
> --------------------------------------------------
>
>                 Key: ZOOKEEPER-161
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-161
>             Project: Zookeeper
>          Issue Type: Sub-task
>          Components: documentation
>    Affects Versions: 3.0.1
>            Reporter: Robbie Scott
>             Fix For: 3.0.1
>
>         Attachments: ZOOKEEPER-161.patch
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> We should document how ops engineer should design their ZooKeeper deployments.  

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


[jira] Commented: (ZOOKEEPER-161) Content needed: "Designing a ZooKeeper Deployment"

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ZOOKEEPER-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655208#action_12655208 ] 

Hudson commented on ZOOKEEPER-161:
----------------------------------

Integrated in ZooKeeper-trunk #168 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/168/])
    . Content needed: "Designing a ZooKeeper Deployment"


> Content needed: "Designing a ZooKeeper Deployment"
> --------------------------------------------------
>
>                 Key: ZOOKEEPER-161
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-161
>             Project: Zookeeper
>          Issue Type: Sub-task
>          Components: documentation
>    Affects Versions: 3.0.1
>            Reporter: Robbie Scott
>            Assignee: Benjamin Reed
>             Fix For: 3.1.0
>
>         Attachments: ZOOKEEPER-161.patch, ZOOKEEPER-161.patch
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> We should document how ops engineer should design their ZooKeeper deployments.  

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


[jira] Updated: (ZOOKEEPER-161) Content needed: "Designing a ZooKeeper Deployment"

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

Patrick Hunt updated ZOOKEEPER-161:
-----------------------------------

    Attachment: ZOOKEEPER-161.patch

I updated the patch to fix a few typos and cleanup the xml formatting.


> Content needed: "Designing a ZooKeeper Deployment"
> --------------------------------------------------
>
>                 Key: ZOOKEEPER-161
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-161
>             Project: Zookeeper
>          Issue Type: Sub-task
>          Components: documentation
>    Affects Versions: 3.0.1
>            Reporter: Robbie Scott
>             Fix For: 3.1.0
>
>         Attachments: ZOOKEEPER-161.patch, ZOOKEEPER-161.patch
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> We should document how ops engineer should design their ZooKeeper deployments.  

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


[jira] Updated: (ZOOKEEPER-161) Content needed: "Designing a ZooKeeper Deployment"

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

Mahadev konar updated ZOOKEEPER-161:
------------------------------------

    Fix Version/s:     (was: 3.0.1)
                   3.1.0

> Content needed: "Designing a ZooKeeper Deployment"
> --------------------------------------------------
>
>                 Key: ZOOKEEPER-161
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-161
>             Project: Zookeeper
>          Issue Type: Sub-task
>          Components: documentation
>    Affects Versions: 3.0.1
>            Reporter: Robbie Scott
>             Fix For: 3.1.0
>
>         Attachments: ZOOKEEPER-161.patch
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> We should document how ops engineer should design their ZooKeeper deployments.  

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


[jira] Updated: (ZOOKEEPER-161) Content needed: "Designing a ZooKeeper Deployment"

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

Robbie Scott updated ZOOKEEPER-161:
-----------------------------------

    Remaining Estimate: 8h  (was: 0.13h)
     Original Estimate: 8h  (was: 0.13h)

> Content needed: "Designing a ZooKeeper Deployment"
> --------------------------------------------------
>
>                 Key: ZOOKEEPER-161
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-161
>             Project: Zookeeper
>          Issue Type: Sub-task
>          Components: documentation
>            Reporter: Robbie Scott
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> We should document how ops engineer should design their ZooKeeper deployments.  

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


[jira] Assigned: (ZOOKEEPER-161) Content needed: "Designing a ZooKeeper Deployment"

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

Patrick Hunt reassigned ZOOKEEPER-161:
--------------------------------------

    Assignee: Benjamin Reed

> Content needed: "Designing a ZooKeeper Deployment"
> --------------------------------------------------
>
>                 Key: ZOOKEEPER-161
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-161
>             Project: Zookeeper
>          Issue Type: Sub-task
>          Components: documentation
>    Affects Versions: 3.0.1
>            Reporter: Robbie Scott
>            Assignee: Benjamin Reed
>             Fix For: 3.1.0
>
>         Attachments: ZOOKEEPER-161.patch, ZOOKEEPER-161.patch
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> We should document how ops engineer should design their ZooKeeper deployments.  

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


[jira] Updated: (ZOOKEEPER-161) Content needed: "Designing a ZooKeeper Deployment"

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

Robbie Scott updated ZOOKEEPER-161:
-----------------------------------

    Attachment: ZOOKEEPER-161.patch

Here's new content, thx Ben!

> Content needed: "Designing a ZooKeeper Deployment"
> --------------------------------------------------
>
>                 Key: ZOOKEEPER-161
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-161
>             Project: Zookeeper
>          Issue Type: Sub-task
>          Components: documentation
>    Affects Versions: 3.0.1
>            Reporter: Robbie Scott
>             Fix For: 3.0.1
>
>         Attachments: ZOOKEEPER-161.patch
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> We should document how ops engineer should design their ZooKeeper deployments.  

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


[jira] Updated: (ZOOKEEPER-161) Content needed: "Designing a ZooKeeper Deployment"

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

Patrick Hunt updated ZOOKEEPER-161:
-----------------------------------

      Resolution: Fixed
    Hadoop Flags: [Reviewed]
          Status: Resolved  (was: Patch Available)

+1, looks good

Committed revision 724936.

> Content needed: "Designing a ZooKeeper Deployment"
> --------------------------------------------------
>
>                 Key: ZOOKEEPER-161
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-161
>             Project: Zookeeper
>          Issue Type: Sub-task
>          Components: documentation
>    Affects Versions: 3.0.1
>            Reporter: Robbie Scott
>            Assignee: Benjamin Reed
>             Fix For: 3.1.0
>
>         Attachments: ZOOKEEPER-161.patch, ZOOKEEPER-161.patch
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> We should document how ops engineer should design their ZooKeeper deployments.  

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