RE: Running Cassandra as a Windows Service
I'll put something together and submit it. Thanks for the help. Todd -Original Message- From: Gary Dusbabek [mailto:gdusba...@gmail.com] Sent: Friday, June 11, 2010 4:49 AM To: user@cassandra.apache.org Subject: Re: Running Cassandra as a Windows Service Sure. Please create a jira ticket (https://issues.apache.org/jira/browse/CASSANDRA) and attach the files you wish to contribute. One of the committers (probably myself) will review them and decide how to integrate them into the project. If it's not too much trouble, an ant build script would be excellent and would help to automate the process of generating testable builds. Gary. On Thu, Jun 10, 2010 at 17:31, Kochheiser,Todd W - TO-DITT1 twkochhei...@bpa.gov wrote: I agree that bitrot might be happen if all of the core Cassandra developers are using Linux. Your suggestion of putting things in a contrib area where curious (or desperate) parties suffering on the Windows platform could pick it up seems like a reasonable place to start. It might also be an opportunity to increase the number of application developers using Cassandra if Cassandra was slightly more approachable on the Windows platform. Any suggestions on next steps? Todd. -Original Message- From: Gary Dusbabek [mailto:gdusba...@gmail.com] Sent: Thursday, June 10, 2010 10:59 AM To: user@cassandra.apache.org Subject: Re: Running Cassandra as a Windows Service IMO this is one of those things that would bitrot fairly quickly if it were not maintained. It may be useful in contrib, where curious parties could pick it up, get it back in shape, and send in the changes to be committed. Judging by the sparse interest so far, this probably wouldn't be a good fit in core since there don't seem to be many (any?) cassandra developers who run windows. Gary. On Thu, Jun 10, 2010 at 12:34, Kochheiser,Todd W - TO-DITT1 twkochhei...@bpa.gov wrote: For various reasons I am required to deploy systems on Windows. As such, I went looking for information on running Cassandra as a Windows service. I've read some of the user threads regarding running Cassandra as a Windows service, such as this one: http://www.mail-archive.com/user@cassandra.apache.org/msg01656.html I also found the following JIRA issue: https://issues.apache.org/jira/browse/CASSANDRA-292 As it didn't look like anyone has contributed a formal solution and having some experience using Apache's Procrun (http://commons.apache.org/daemon/procrun.html), I decided to go ahead and write a batch script and a simple WindowsService class to accomplish the task. The WindowsService class only makes calls to public methods in CassandraDeamon and is fairly simple. In combination with the batch script, it is very easy to install and remove the service. At this point, I've installed Cassandra as a Windows service on XP (32 bit), Windows 7 (64 bit) and Windows Server 2008 R1/R2 (64 bit). It should work fine on other version of Windows (2K, 2K3). Questions: Has anyone else already done this work? If not, I wouldn't mind sharing the code/script or contributing it back to the project. Is there any interest in this from the Cassandra dev team or the user community? Ideally the WindowsService could be included in the distributed source/binary distributions (perhaps in a contrib area) as well as the batch script and associated procrun executables. Or, perhaps it could be posted to a Cassandra community site (is there one?). Todd
RE: Pelops - a new Java client library paradigm
Great API that looks easy and intuitive to use. Regarding your connection pool implementation, how does it handle failed/crashed nodes? Will the pool auto-detect failed nodes via a tester thread or will a failed node, and hence its pooled connection(s), be removed only when they are used? Conversely, how will the pool be repopulated once the failed/crashed node becomes available? Todd From: Dominic Williams [mailto:thedwilli...@googlemail.com] Sent: Friday, June 11, 2010 7:05 AM To: user@cassandra.apache.org Subject: Re: Pelops - a new Java client library paradigm Hi good question. The scalability of Pelops is dependent on Cassandra, not the library itself. The library aims to provide an more effective access layer on top of the Thrift API. The library does perform connection pooling, and you can control the size of the pool and other parameters using a policy object. But connection pooling itself does not increase scalability, only efficiency. Hope this helps. BEst, Dominic On 11 June 2010 14:47, Ian Soboroff isobor...@gmail.commailto:isobor...@gmail.com wrote: Sounds nice. Can you say something about the scales at which you've used this library? Both write and read load? Size of clusters and size of data? Ian On Fri, Jun 11, 2010 at 9:41 AM, Dominic Williams thedwilli...@googlemail.commailto:thedwilli...@googlemail.com wrote: Pelops is a new high quality Java client library for Cassandra. It has a design that: * reveals the full power of Cassandra through an elegant Mutator and Selector paradigm * generates better, cleaner, less bug prone code * reduces the learning curve for new users * drives rapid application development * encapsulates advanced pooling algorithms An article introducing Pelops can be found at http://ria101.wordpress.com/2010/06/11/pelops-the-beautiful-cassandra-database-client-for-java/ Thanks for reading. Best, Dominic
RE: Pelops - a new Java client library paradigm
I checked out the source and noticed a few things: 1. You did not include an Ant build file. Not a big deal, but if you happen to have one it would be nice to have. 2. It appears you built against Cassandra 0.6.0. Have you built and/or run Pelops against 0.6.2 or trunk? Todd From: Dominic Williams [mailto:thedwilli...@googlemail.com] Sent: Friday, June 11, 2010 6:42 AM To: user@cassandra.apache.org Subject: Pelops - a new Java client library paradigm Pelops is a new high quality Java client library for Cassandra. It has a design that: * reveals the full power of Cassandra through an elegant Mutator and Selector paradigm * generates better, cleaner, less bug prone code * reduces the learning curve for new users * drives rapid application development * encapsulates advanced pooling algorithms An article introducing Pelops can be found at http://ria101.wordpress.com/2010/06/11/pelops-the-beautiful-cassandra-database-client-for-java/ Thanks for reading. Best, Dominic
Running Cassandra as a Windows Service
For various reasons I am required to deploy systems on Windows. As such, I went looking for information on running Cassandra as a Windows service. I've read some of the user threads regarding running Cassandra as a Windows service, such as this one: http://www.mail-archive.com/user@cassandra.apache.org/msg01656.html I also found the following JIRA issue: https://issues.apache.org/jira/browse/CASSANDRA-292 As it didn't look like anyone has contributed a formal solution and having some experience using Apache's Procrun (http://commons.apache.org/daemon/procrun.html), I decided to go ahead and write a batch script and a simple WindowsService class to accomplish the task. The WindowsService class only makes calls to public methods in CassandraDeamon and is fairly simple. In combination with the batch script, it is very easy to install and remove the service. At this point, I've installed Cassandra as a Windows service on XP (32 bit), Windows 7 (64 bit) and Windows Server 2008 R1/R2 (64 bit). It should work fine on other version of Windows (2K, 2K3). Questions: 1. Has anyone else already done this work? 2. If not, I wouldn't mind sharing the code/script or contributing it back to the project. Is there any interest in this from the Cassandra dev team or the user community? Ideally the WindowsService could be included in the distributed source/binary distributions (perhaps in a contrib area) as well as the batch script and associated procrun executables. Or, perhaps it could be posted to a Cassandra community site (is there one?). Todd
RE: Running Cassandra as a Windows Service
I agree that bitrot might be happen if all of the core Cassandra developers are using Linux. Your suggestion of putting things in a contrib area where curious (or desperate) parties suffering on the Windows platform could pick it up seems like a reasonable place to start. It might also be an opportunity to increase the number of application developers using Cassandra if Cassandra was slightly more approachable on the Windows platform. Any suggestions on next steps? Todd. -Original Message- From: Gary Dusbabek [mailto:gdusba...@gmail.com] Sent: Thursday, June 10, 2010 10:59 AM To: user@cassandra.apache.org Subject: Re: Running Cassandra as a Windows Service IMO this is one of those things that would bitrot fairly quickly if it were not maintained. It may be useful in contrib, where curious parties could pick it up, get it back in shape, and send in the changes to be committed. Judging by the sparse interest so far, this probably wouldn't be a good fit in core since there don't seem to be many (any?) cassandra developers who run windows. Gary. On Thu, Jun 10, 2010 at 12:34, Kochheiser,Todd W - TO-DITT1 twkochhei...@bpa.gov wrote: For various reasons I am required to deploy systems on Windows. As such, I went looking for information on running Cassandra as a Windows service. I've read some of the user threads regarding running Cassandra as a Windows service, such as this one: http://www.mail-archive.com/user@cassandra.apache.org/msg01656.html I also found the following JIRA issue: https://issues.apache.org/jira/browse/CASSANDRA-292 As it didn't look like anyone has contributed a formal solution and having some experience using Apache's Procrun (http://commons.apache.org/daemon/procrun.html), I decided to go ahead and write a batch script and a simple WindowsService class to accomplish the task. The WindowsService class only makes calls to public methods in CassandraDeamon and is fairly simple. In combination with the batch script, it is very easy to install and remove the service. At this point, I've installed Cassandra as a Windows service on XP (32 bit), Windows 7 (64 bit) and Windows Server 2008 R1/R2 (64 bit). It should work fine on other version of Windows (2K, 2K3). Questions: Has anyone else already done this work? If not, I wouldn't mind sharing the code/script or contributing it back to the project. Is there any interest in this from the Cassandra dev team or the user community? Ideally the WindowsService could be included in the distributed source/binary distributions (perhaps in a contrib area) as well as the batch script and associated procrun executables. Or, perhaps it could be posted to a Cassandra community site (is there one?). Todd
