See http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/31/changes
Changes:
[akornev] Replaced a java 6 method with a java 5 equivalent
[phunt] Added initial skeleton for ZOOKEEPER-70
--
[...truncated 16285 lines...]
[junit] at
org.apache.z
[
https://issues.apache.org/jira/browse/ZOOKEEPER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615954#action_12615954
]
james strachan commented on ZOOKEEPER-83:
-
Note its pretty trivial to maintain an
2008/7/22 Hiram Chirino <[EMAIL PROTECTED]>:
> Lol.. Apache infrastructure supports multiple wiki backends. It's up
> to the project to pick which one you want to you. You currently have
> picked MoinMoin, but you could have easily picked Confluence, just
> like these other Apache projects did:
>
[
https://issues.apache.org/jira/browse/ZOOKEEPER-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615957#action_12615957
]
james strachan commented on ZOOKEEPER-84:
-
I'm kinda confused by that :)
So what
2008/7/22 Flavio Junqueira <[EMAIL PROTECTED]>:
> James, I'd like to clarify what exactly is the issue you're looking at. If
> you provide a list of ZooKeeper servers, then a client will try to reconnect
> to another ZooKeeper server upon a disconnection. Reconnecting to another
> server does not g
Many apache projects including Hadoop register with nabble to host
online forums & great online archives of the mailing lists...
http://www.nabble.com/Hadoop-f17066.html
Currently there's hadoop-core, hbase and lucene on there.
I often refer to mailing list posts by nabble link; they're really
han
Am just wondering if I've hit this due to some other bug. I thought ZK
did keep-alive pings to ensure each client is alive and its session
does not expire? Or does the client have to explicitly keep calling
some method on the ZooKeeper interface to ensure a steady flow of
packets to the ZK server t
[
https://issues.apache.org/jira/browse/ZOOKEEPER-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616012#action_12616012
]
james strachan commented on ZOOKEEPER-84:
-
the ZooKeeper will reconnect by defaul
BTW one other observation; when I use 3 clients in the same JVM (i.e.
3 separate instances of ZooKeeper to try simulate a set of different
processes) I find that each client receives an initial WatchEvent on
startup; then from that point on, only the first 2 clients receive
further watch events for
[
https://issues.apache.org/jira/browse/ZOOKEEPER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616020#action_12616020
]
Hiram Chirino commented on ZOOKEEPER-83:
James is right.
An ant build could easi
[
https://issues.apache.org/jira/browse/ZOOKEEPER-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616025#action_12616025
]
Hiram Chirino commented on ZOOKEEPER-82:
Anybody have a chance to review the patc
How big is the ZooKeeper developer community and what commercial
associations do they have?
--
Regards,
Hiram
Blog: http://hiramchirino.com
Open Source SOA
http://open.iona.com
[
https://issues.apache.org/jira/browse/ZOOKEEPER-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616039#action_12616039
]
Benjamin Reed commented on ZOOKEEPER-84:
The problem with the reconnect method is
SessionExpiredExceptions should be extremely rare. Basically they should only
happen if a machine goes down (of course that would mean no exception would
actually get generated since the client is dead :) or a network partition
occurs.
Having said that we seem to have a bug that cause SessionEx
[
https://issues.apache.org/jira/browse/ZOOKEEPER-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616065#action_12616065
]
james strachan commented on ZOOKEEPER-84:
-
I hear you :)
So an Elect Leader or W
2008/7/23 Benjamin Reed <[EMAIL PROTECTED]>:
> SessionExpiredExceptions should be extremely rare. Basically they should only
> happen if a machine goes down (of course that would mean no exception would
> actually get generated since the client is dead :) or a network partition
> occurs.
>
> Having
[
https://issues.apache.org/jira/browse/ZOOKEEPER-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616114#action_12616114
]
james strachan commented on ZOOKEEPER-84:
-
You can mark this issue as RESOLVED/WI
[
https://issues.apache.org/jira/browse/ZOOKEEPER-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
james strachan updated ZOOKEEPER-78:
Attachment: using_zookeeper_facade.patch
This patch no longer requires ZOOKEEPER-84, we n
2008/7/23 James Strachan <[EMAIL PROTECTED]>:
> 2008/7/23 Benjamin Reed <[EMAIL PROTECTED]>:
>> SessionExpiredExceptions should be extremely rare. Basically they should only
>> happen if a machine goes down (of course that would mean no exception would
>> actually get generated since the client is
I've always had some tests failing on most boxes I try; I wasn't sure
if everyone else got those or if they do work on some platforms?
On OS X I get these failures
[junit] Test org.apache.zookeeper.test.AsyncTest FAILED
[junit] Test org.apache.zookeeper.test.WatcherFuncTest FAILED
On a li
[
https://issues.apache.org/jira/browse/ZOOKEEPER-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
james strachan updated ZOOKEEPER-78:
Assignee: (was: james strachan)
Status: Patch Available (was: Open)
Patch is n
I'm on ubuntu (hardy heron) and they work. Our CI machine has
intermittent failures (solaris x86):
http://hudson.zones.apache.org/hudson/view/ZooKeeper/job/ZooKeeper-trunk/
there's some timing issue, what you're seeing is probably related to:
https://issues.apache.org/jira/browse/ZOOKEEPER-61
F
[
https://issues.apache.org/jira/browse/ZOOKEEPER-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616136#action_12616136
]
james strachan commented on ZOOKEEPER-63:
-
I wonder if I've seen this too - I can
I was going to refer you guys to
https://issues.apache.org/jira/browse/ZOOKEEPER-63
but I noticed in the comments James beat me to it! :-)
Ben, you had an idea for how to address 63, please add a comment (I
think it was to set the state to closed before sending the disconnect
request to the ser
FWIW I've ran the tests a few times; I think all these 4 tests have
timing failures in them. I've seen all of them fail on OS X at some
point. Sometimes only 2 will fail. On Linux I've seen just ClientTest
fail.
2008/7/23 Patrick Hunt <[EMAIL PROTECTED]>:
> I'm on ubuntu (hardy heron) and they wo
[
https://issues.apache.org/jira/browse/ZOOKEEPER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616139#action_12616139
]
Benjamin Reed commented on ZOOKEEPER-83:
I completely agreed with the goals you a
[
https://issues.apache.org/jira/browse/ZOOKEEPER-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616140#action_12616140
]
Patrick Hunt commented on ZOOKEEPER-84:
---
This has been a really interesting discuss
[
https://issues.apache.org/jira/browse/ZOOKEEPER-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt reassigned ZOOKEEPER-84:
-
Assignee: Benjamin Reed (was: james strachan)
Assigning to Ben to document on the wiki
Just an idle observation as I'd never seen this workflow before on
JIRA so thought I'd ask :)
I've been watching some of the recent JIRA activity with interest.
I've seen a few JIRAs arrive, someone submits a test case who's not a
committer, then the issue gets assigned to the person who submitted
[
https://issues.apache.org/jira/browse/ZOOKEEPER-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616144#action_12616144
]
james strachan commented on ZOOKEEPER-84:
-
If ZOOKEEPER-78 ever gets committed (h
Good question, according to the PoweredBy wiki not too much ;-)
http://wiki.apache.org/hadoop/ZooKeeper/PoweredBy
(please update this if your company is using...)
So far we have 5 committers (Ben, Andrew, Flavio, Mahadev and myself)
and just a few contributors.
There are a number of teams usin
Good idea. Please enter a Jira and assign it to me.
Patrick
James Strachan wrote:
Many apache projects including Hadoop register with nabble to host
online forums & great online archives of the mailing lists...
http://www.nabble.com/Hadoop-f17066.html
Currently there's hadoop-core, hbase and l
[
https://issues.apache.org/jira/browse/ZOOKEEPER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616149#action_12616149
]
james strachan commented on ZOOKEEPER-83:
-
So long as dependencies don't change m
Done
https://issues.apache.org/jira/browse/ZOOKEEPER-85
2008/7/23 Patrick Hunt <[EMAIL PROTECTED]>:
> Good idea. Please enter a Jira and assign it to me.
>
> Patrick
>
>
> James Strachan wrote:
>>
>> Many apache projects including Hadoop register with nabble to host
>> online forums & great online
register the ZooKeeper mailing lists with nabble.com
Key: ZOOKEEPER-85
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-85
Project: Zookeeper
Issue Type: Task
Reporter: jam
Best bet is to put it to the vote - create a Jira. I'll make sure we get
input from Hadoop PMC and core team members.
Patrick
James Strachan wrote:
2008/7/22 Hiram Chirino <[EMAIL PROTECTED]>:
Lol.. Apache infrastructure supports multiple wiki backends. It's up
to the project to pick which o
[
https://issues.apache.org/jira/browse/ZOOKEEPER-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616151#action_12616151
]
james strachan commented on ZOOKEEPER-63:
-
BTW here's the hang I seem to be able
James Strachan wrote:
Just an idle observation as I'd never seen this workflow before on
JIRA so thought I'd ask :)
I'm new to JIRA as well...
I've been watching some of the recent JIRA activity with interest.
I've seen a few JIRAs arrive, someone submits a test case who's not a
committer, th
[
https://issues.apache.org/jira/browse/ZOOKEEPER-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
james strachan updated ZOOKEEPER-63:
Attachment: patch_ZOOKEEPER-63.patch
This patch avoids the close() method blocking foreve
[
https://issues.apache.org/jira/browse/ZOOKEEPER-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
james strachan updated ZOOKEEPER-63:
Status: Patch Available (was: Open)
about to attach a patch
> Race condition in client
It's important to capture this type of information in jira.
James Strachan wrote:
FWIW I've ran the tests a few times; I think all these 4 tests have
timing failures in them. I've seen all of them fail on OS X at some
point. Sometimes only 2 will fail. On Linux I've seen just ClientTest
fail.
Cool thanks for the heads up! You live and learn :) Its funny how
totally different all the various Apache projects are and how they get
things done.
My bad for not reading the contributing section of the wiki yet :)
2008/7/23 Patrick Hunt <[EMAIL PROTECTED]>:
> James Strachan wrote:
>>
>> Just a
intermittent test failure of org.apache.zookeeper.test.AsyncTest
Key: ZOOKEEPER-86
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-86
Project: Zookeeper
Issue Type: Bug
[
https://issues.apache.org/jira/browse/ZOOKEEPER-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
james strachan updated ZOOKEEPER-86:
Attachment: TEST-org.apache.zookeeper.test.AsyncTest.txt
here's the output when ran on OS
James Strachan wrote:
Tools like wikis are personal things; and folks tend to prefer to use
the tool they know.
That's a key point.
To make a switch you'd need:
1. Someone familiar with Confluence to lead the transition, convert
the existing website and wiki content, set up static export etc
[
https://issues.apache.org/jira/browse/ZOOKEEPER-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616164#action_12616164
]
Patrick Hunt commented on ZOOKEEPER-82:
---
select "submit patch" so that it will be m
Regardless of which wiki we use the documentation is in Forrest and
checked into SVN. Forrest is used both to write the docs (which are
versioned along with the code) as well as generating the
hadoop.apache.org web site. (trunk/src/docs) We have a tech writer who
is currently migrating the sour
Makes sense. Feel free to do so.
mahadev
On 7/23/08 9:12 AM, "James Strachan" <[EMAIL PROTECTED]> wrote:
> FWIW I've ran the tests a few times; I think all these 4 tests have
> timing failures in them. I've seen all of them fail on OS X at some
> point. Sometimes only 2 will fail. On Linux I'v
Actually not your bad, I just added that page last night. ;-)
I really appreciate your (everyone) input and it's helping to shape our
decisions as a new Apache project. I know that everyone is super excited
to run with ZooKeeper, we (existing project members) are excited as
well. Bear with us
[
https://issues.apache.org/jira/browse/ZOOKEEPER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616174#action_12616174
]
Doug Cutting commented on ZOOKEEPER-83:
---
> I believe there is a way to use ANT to c
2008/7/23 Doug Cutting <[EMAIL PROTECTED]>:
> James Strachan wrote:
>>
>> Tools like wikis are personal things; and folks tend to prefer to use
>> the tool they know.
>
> That's a key point.
>
> To make a switch you'd need:
> 1. Someone familiar with Confluence to lead the transition, convert the
[
https://issues.apache.org/jira/browse/ZOOKEEPER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616200#action_12616200
]
Hiram Chirino commented on ZOOKEEPER-83:
Hi folks..
To make the maven re-org su
[
https://issues.apache.org/jira/browse/ZOOKEEPER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616200#action_12616200
]
chirino edited comment on ZOOKEEPER-83 at 7/23/08 11:18 AM:
---
[
https://issues.apache.org/jira/browse/ZOOKEEPER-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt resolved ZOOKEEPER-85.
---
Resolution: Fixed
user and dev lists are now registered with nabble
http://n2.nabble.com/z
Both the user and dev lists are now being archived on nabble.
http://n2.nabble.com/zookeeper-dev-f578911.html
http://n2.nabble.com/zookeeper-user-f578899.html
Patrick
Awesome :)
2008/7/23 Patrick Hunt <[EMAIL PROTECTED]>:
> Both the user and dev lists are now being archived on nabble.
>
> http://n2.nabble.com/zookeeper-dev-f578911.html
> http://n2.nabble.com/zookeeper-user-f578899.html
>
> Patrick
>
--
James
---
http://macstrac.blogspot.com/
Open Sourc
Follower does not shut itself down if its too far behind the leader.
Key: ZOOKEEPER-87
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-87
Project: Zookeeper
Issue Type
[
https://issues.apache.org/jira/browse/ZOOKEEPER-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahadev konar updated ZOOKEEPER-87:
---
Fix Version/s: 3.0.0
> Follower does not shut itself down if its too far behind the leader.
James Strachan wrote:
Incidentally a totally different thought; whats gonna be the split
between whats the static website (e.g. Forrest) versus stuff thats in
the wiki versus documentation that goes inside each release? Its often
a kinda slippery slope figuring out which bit does what
Official
[
https://issues.apache.org/jira/browse/ZOOKEEPER-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
james strachan updated ZOOKEEPER-86:
Status: Patch Available (was: Open)
about to attach
> intermittent test failure of org.
Here's the first issue with a patch...
https://issues.apache.org/jira/browse/ZOOKEEPER-86
2008/7/23 Patrick Hunt <[EMAIL PROTECTED]>:
> It's important to capture this type of information in jira.
>
> James Strachan wrote:
>>
>> FWIW I've ran the tests a few times; I think all these 4 tests have
>>
[
https://issues.apache.org/jira/browse/ZOOKEEPER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated ZOOKEEPER-83:
---
Assignee: (was: Hiram Chirino)
Status: Patch Available (was: Open)
> Switch to u
[
https://issues.apache.org/jira/browse/ZOOKEEPER-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated ZOOKEEPER-82:
---
Assignee: (was: Hiram Chirino)
Status: Patch Available (was: Open)
> Make the Zo
[
https://issues.apache.org/jira/browse/ZOOKEEPER-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
james strachan updated ZOOKEEPER-86:
Attachment: patch_for_ZOOKEEPER-86.patch
this patch seems to fix the test case on OS X at
So all the commiters are Yahoo folks?
On Wed, Jul 23, 2008 at 12:24 PM, Patrick Hunt <[EMAIL PROTECTED]> wrote:
> Good question, according to the PoweredBy wiki not too much ;-)
> http://wiki.apache.org/hadoop/ZooKeeper/PoweredBy
> (please update this if your company is using...)
>
> So far we hav
[
https://issues.apache.org/jira/browse/ZOOKEEPER-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616219#action_12616219
]
Patrick Hunt commented on ZOOKEEPER-63:
---
Correct me if I'm wrong but I don't believ
Personally, I think forest is the right thing to do regarding product
documentation (manuals, api docs, user docs). It very version
specific and needs to stay with the source code.
That said, project information is NOT product or version specific.
The general website could get generated from the
Yes, it's documented on the web site:
http://hadoop.apache.org/zookeeper/credits.html
Patrick
Hiram Chirino wrote:
So all the commiters are Yahoo folks?
On Wed, Jul 23, 2008 at 12:24 PM, Patrick Hunt <[EMAIL PROTECTED]> wrote:
Good question, according to the PoweredBy wiki not too much ;-)
ht
Yes they are!
mahadev
On 7/23/08 11:47 AM, "Hiram Chirino" <[EMAIL PROTECTED]> wrote:
> So all the commiters are Yahoo folks?
>
> On Wed, Jul 23, 2008 at 12:24 PM, Patrick Hunt <[EMAIL PROTECTED]> wrote:
>> Good question, according to the PoweredBy wiki not too much ;-)
>> http://wiki.apache.o
Hope your mentors have mentioned that diversity is a good thing. Also
how did you guys bypass the incubator?
On Wed, Jul 23, 2008 at 2:50 PM, Mahadev Konar <[EMAIL PROTECTED]> wrote:
> Yes they are!
>
> mahadev
>
>
> On 7/23/08 11:47 AM, "Hiram Chirino" <[EMAIL PROTECTED]> wrote:
>
>> So all the
Hiram Chirino wrote:
So all the commiters are Yahoo folks?
Yes, so far. Hadoop's PMC oversees Zookeeper, and it's not all Y!.
http://hadoop.apache.org/who.html
Zookeeper hasn't yet been at Apache long. We hope to soon add non-Y!
committers to Zookeeper, and are on the watch for folks with
Hiram Chirino wrote:
Hope your mentors have mentioned that diversity is a good thing.
Indeed.
Also how did you guys bypass the incubator?
The IP title was clear (entirely covered by a software grant from Y!)
and the Hadoop PMC was willing to guide the project.
Doug
[
https://issues.apache.org/jira/browse/ZOOKEEPER-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616223#action_12616223
]
Benjamin Reed commented on ZOOKEEPER-78:
Fantastic work! I second Hiram's suggest
We are fully aware of that Hiram. We are still a sub project of Hadoop and
have been on sourceforge for a while. For being a sub project the Hadoop PMC
needs to vote for it. Zookeeper is in the future roadmap of Hadoop for High
Availability/ configuration management and mounting of different
filesy
On Wed, Jul 23, 2008 at 3:03 PM, Mahadev Konar <[EMAIL PROTECTED]> wrote:
> We are fully aware of that Hiram. We are still a sub project of Hadoop and
> have been on sourceforge for a while. For being a sub project the Hadoop PMC
> needs to vote for it. Zookeeper is in the future roadmap of Hadoop
>
> Are all you guys also PMC members on Hadoop?
>
Never mind.. I just looked it up in the asf-authorization file.
hadoop-zookeeper=akornev,breed,fpj,mahadev,phunt
hadoop-pmc=ab,cutting,dhruba,enis,jimk,nigel,omalley,stack,taton,tomwhite
looks like you guys are not in the PMC. Sorry about that.
Hiram Chirino wrote:
looks like you guys are not in the PMC. Sorry about that. But it
bring us a weird governance issue which is very anti Apahe.. usually
an Apache project is self governed, but from the look of the
authorization file, it seems like the zookeeper committers cannot
properly sel
Ok good... as long as the PMC folks are participating it should not
be a problem.
Regards,
Hiram
On Wed, Jul 23, 2008 at 4:12 PM, Doug Cutting <[EMAIL PROTECTED]> wrote:
> Hiram Chirino wrote:
>>
>> looks like you guys are not in the PMC. Sorry about that. But it
>> bring us a weird governance
[
https://issues.apache.org/jira/browse/ZOOKEEPER-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616257#action_12616257
]
Flavio Paiva Junqueira commented on ZOOKEEPER-79:
-
I have added a descrip
[
https://issues.apache.org/jira/browse/ZOOKEEPER-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-81:
--
Affects Version/s: 3.0.0
Fix Version/s: 3.0.0
Fixed in 3.0.0
> JMX module is using 1
[
https://issues.apache.org/jira/browse/ZOOKEEPER-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on ZOOKEEPER-80 started by Patrick Hunt.
> Document process for client recipe contributions
>
>
>
[
https://issues.apache.org/jira/browse/ZOOKEEPER-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on ZOOKEEPER-80 stopped by Patrick Hunt.
> Document process for client recipe contributions
>
>
>
82 matches
Mail list logo
