Return-Path: X-Original-To: apmail-zookeeper-user-archive@www.apache.org Delivered-To: apmail-zookeeper-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0A4071063A for ; Mon, 13 Jan 2014 09:45:02 +0000 (UTC) Received: (qmail 55431 invoked by uid 500); 13 Jan 2014 09:44:43 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 55376 invoked by uid 500); 13 Jan 2014 09:44:36 -0000 Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@zookeeper.apache.org Delivered-To: mailing list user@zookeeper.apache.org Received: (qmail 55342 invoked by uid 99); 13 Jan 2014 09:44:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Jan 2014 09:44:32 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [213.199.154.187] (HELO db8outboundpool.messaging.microsoft.com) (213.199.154.187) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Jan 2014 09:44:26 +0000 Received: from mail105-db8-R.bigfish.com (10.174.8.227) by DB8EHSOBE027.bigfish.com (10.174.4.90) with Microsoft SMTP Server id 14.1.225.22; Mon, 13 Jan 2014 09:44:05 +0000 Received: from mail105-db8 (localhost [127.0.0.1]) by mail105-db8-R.bigfish.com (Postfix) with ESMTP id ED47F8600F9 for ; Mon, 13 Jan 2014 09:44:05 +0000 (UTC) X-Forefront-Antispam-Report: CIP:213.86.77.6;KIP:(null);UIP:(null);IPV:NLI;H:emea-tc2-edge02.sungard.com;RD:none;EFVD:NLI X-SpamScore: -6 X-BigFish: VPS-6(zzdb82h98dI9371I550I1454I542I1432I4015Izz1f42h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21a7h1fc6hzz1de098h177df4h17326ah8275bh8275dh1de097h186068h17c832iz2dh109h2a8h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h1ad9h1b0ah1b2fh2222h224fh1fb3h1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1fe8h1ff5h2216h22d0h2336h2438h2461h1155h) Received: from mail105-db8 (localhost.localdomain [127.0.0.1]) by mail105-db8 (MessageSwitch) id 1389606243781215_18911; Mon, 13 Jan 2014 09:44:03 +0000 (UTC) Received: from DB8EHSMHS008.bigfish.com (unknown [10.174.8.230]) by mail105-db8.bigfish.com (Postfix) with ESMTP id BA0D1840047 for ; Mon, 13 Jan 2014 09:44:03 +0000 (UTC) Received: from emea-tc2-edge02.sungard.com (213.86.77.6) by DB8EHSMHS008.bigfish.com (10.174.4.18) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 13 Jan 2014 09:44:03 +0000 Received: from EMEA-TC2-CAS01.internal.sungard.corp (10.254.236.2) by emea-tc2-edge02.sungard.com (213.86.77.6) with Microsoft SMTP Server (TLS) id 14.3.169.1; Mon, 13 Jan 2014 09:43:57 +0000 Received: from EMEA-TC2-MB02.internal.sungard.corp ([169.254.2.61]) by emea-tc2-cas01.internal.sungard.corp ([10.254.236.2]) with mapi id 14.03.0169.001; Mon, 13 Jan 2014 09:44:02 +0000 From: To: Subject: RE: Windows support (Win-64) Thread-Topic: Windows support (Win-64) Thread-Index: AQHPC3pHyx7a9jquIUWRzpNfQUDWSJp5k3+AgADKNQCAASTzgIAAMUQAgAFMooCAALMm4IAAiFSAgAA+CwCAA/ZvIA== Date: Mon, 13 Jan 2014 09:44:01 +0000 Message-ID: <7B36F63619C46A49B86E0D5AB8CDD20061742A24@emea-tc2-mb02.internal.sungard.corp> References: <7B36F63619C46A49B86E0D5AB8CDD200617415C0@emea-tc2-mb02.internal.sungard.corp> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.254.236.238] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: sungard.com X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% X-Virus-Checked: Checked by ClamAV on apache.org Will do! We're interested in using it from .NET, but the primary point is t= o get the server supported, and then we can choose our method of access fro= m .NET (e.g. wrap the C client or use the ZookeeperNet package etc) Thanks, Ben -----Original Message----- From: Patrick Hunt [mailto:phunt@apache.org]=20 Sent: 10 January 2014 21:11 To: UserZooKeeper Subject: Re: Windows support (Win-64) Just back from vacation and didn't notice a number of folks are looking at = this: https://issues.apache.org/jira/browse/ZOOKEEPER-1833 Kudos! Ben feel free to jump in and participate. Regards, Patrick On Fri, Jan 10, 2014 at 9:29 AM, Patrick Hunt wrote: > Hi Ben, if you were interested to help drive windows support that=20 > would be great. I'd be happy to help support. Note that Michi has been=20 > doing work on this already, you probably have seen that on the ML=20 > archive and the JIRA. I suggest you look there if you want to get more=20 > insight into activity/progress. > > In terms of what you might do, take a look a our CI env=20 > https://builds.apache.org/view/S-Z/view/ZooKeeper/ > notice that we have three builds running on windows, some with vs2008 > > Likely you'd want to run the same but in your environment, probably on > 3.4.5 release > > It would be great if you could enter JIRAs/patches for the things you=20 > find. If you're "comfortable" at some point then I don't see why we=20 > couldn't update the docs and make it official in an upcoming release. > > Regards, > > Patrick > > On Fri, Jan 10, 2014 at 1:24 AM, wrote: >> We would certain be interested in helping giving feedback on the server = stability on Windows. I'm trying to push for increased adoption of Zookeepe= r in the org, but the message in the docs itself puts off my managers a bit= from pushing full ahead, so it's a bit of a chicken and egg situation. If = there are test suites we can run to help you out I can look at running them= here on Windows... >> >> Thanks, >> Ben >> >> -----Original Message----- >> From: Patrick Hunt [mailto:phunt@apache.org] >> Sent: 09 January 2014 22:40 >> To: UserZooKeeper >> Subject: Re: Windows support (Win-64) >> >> On Wed, Jan 8, 2014 at 6:49 PM, Salabhanjika S = wrote: >>>> afaik there is no reason it should work on windows. >>> >>> Patrick, I got more confused by your statement. Did you mean "no=20 >>> reason it should *NOT* to work on Windows"? I will be very happy if=20 >>> that is what you meant. >> >> Oops, sorry about that. I meant to write "no reason it shouldn't=20 >> work". afaik the java server/client should work. As mentioned=20 >> previously in the thread the C client may not at the moment but in=20 >> general some folks have had success in the past. (this is what I was=20 >> trying to get at before wrt the scope of use and feedback on windows=20 >> has been limited) >> >> Patrick >> >>> I can say at least 3 of my clients (past & current) asked for=20 >>> Windows support. Though I don't see a reason for *NOT TO WORK* on=20 >>> Windows, I could not confidently convince them due to official (read=20 >>> conservative as Pat >>> mentioned) limitation in documentation (Admin guide). >>> >>> I agree on our concerns w.r.to community usage and support. >>> IMHO, we should remove this limitation (in worst case for Server and=20 >>> Java based Clients) immediately from Admin guide and work on issues=20 >>> w.r.to other clients. >>> >>> Just for information only. >>> Hortonworks claims they will be supporting(in NEAR future release)=20 >>> distribution on Windows as well. >>> http://hortonworks.com/products/hdp-windows/ >>> >>> >>> >>> On Thu, Jan 9, 2014 at 5:23 AM, Patrick Hunt wrote: >>> >>>> This is us being our typical conservative selves. ;-) afaik there=20 >>>> is no reason it should work on windows. I think our main concern=20 >>>> has been having folks actually using it on windows and reporting=20 >>>> back good experiences (any windows reports at all have been limited=20 >>>> so >>>> far) and also having enough community members interested in windows=20 >>>> such that when an issue does come up there will be someone=20 >>>> willing/interested/able to resolve the issue. >>>> >>>> Patrick >>>> >>>> On Tue, Jan 7, 2014 at 10:24 PM, Rakesh R wrote: >>>> > Hi Salabhanjika, >>>> > >>>> > I've used zk client(java) in windows platform during development pha= se. >>>> I personally feel, java server and java clients would work well in=20 >>>> windows environment and there will not be much issues. But truly=20 >>>> speaking I haven't tested thoroughly (java)zk server in windows=20 >>>> platform. Adding one more, recently few efforts has been taken to=20 >>>> stabilize Jenkins(Windows) and is in progress. I think this will give = more confidence to all. >>>> > >>>> > https://builds.apache.org/job/ZooKeeper-3.4-WinVS2008_java/ >>>> > https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008_java >>>> > >>>> > -Rakesh >>>> > >>>> > -----Original Message----- >>>> > From: Salabhanjika S [mailto:salabhanjika9@gmail.com] >>>> > Sent: 07 January 2014 23:51 >>>> > To: user@zookeeper.apache.org >>>> > Subject: Re: Windows support (Win-64) >>>> > >>>> > Seems I'm not the first one to be misguided by documentation. >>>> > https://issues.apache.org/jira/browse/ZOOKEEPER-1635 >>>> > >>>> > Added a comment in this issue too. >>>> > >>>> > I interpret above jira as, C Client issue for Win-64 alone. If=20 >>>> > that is >>>> the case, should it more clear from documentation (admin guide). >>>> > >>>> > - Windows (win32 & win64) is supported as a *development and=20 >>>> > production >>>> > platform* for both server and client (java client only). ZK-1635 >>>> reference can be provided here. >>>> > >>>> > Rationale behind this proposal is to bring more confidence to=20 >>>> > ZooKeeper >>>> users on Windows. >>>> > >>>> > On Tue, Jan 7, 2014 at 12:51 PM, Salabhanjika S=20 >>>> >>>> >wrote: >>>> > >>>> >> Does ZooKeeper is supported on Windows (Win-64). When I searched=20 >>>> >> through the mailing list, I found=20 >>>> >> http://search-hadoop.com/m/pyVQoOgNQc/windows&subj=3DZooKeeper+on+ >>>> >> Wi >>>> >> ndow >>>> >> s >>>> >> >>>> >> >>>> >> As per this discussion, there is no restriction/limitation as such. >>>> >> But documentations claims "development only" support on Windows(Win= -32). >>>> >> >>>> >> >>>> >> http://zookeeper.apache.org/doc/trunk/zookeeperAdmin.html#sc_sup >>>> >> po >>>> >> rted >>>> >> Platforms >>>> >> >>>> >> >>>> >> Should this be a documentation fix? >>>> >> >>>> >> >>