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
___
in production we are ourselves will switch it off (although note the worse
downside is that the occasional network error to a node will cause the
refreshing of its pool)
Hope this makes sense.
Best, Dominic
On 14 June 2010 15:32, Kochheiser,Todd W - TO-DITT1
mailto:twkochhei...@bpa.gov>>
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? C
ld help to automate the process of generating testable builds.
Gary.
On Thu, Jun 10, 2010 at 17:31, Kochheiser,Todd W - TO-DITT1
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 wher
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
wrote:
> For various reasons
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@ca
