Hi--
It's trivial to do this in Kubernetes, even without Ubernetes. Please feel
free to send me a note and I'll walk you through it.
Disclosure: I work on Google on Kubernetes.
On Thu, Apr 14, 2016 at 9:10 AM Joe Stein wrote:
> You can do that with the Mesos scheduler
>
My thinking was that due to the size of the data that there maybe I/O issues.
But it sounds more like you're competing for locks and hit a deadlock issue.
Regards,
Denise
Cell - (860)989-3431
Sent from mi iPhone
> On Apr 15, 2016, at 9:00 AM, horschi wrote:
>
> Hi Denise,
Thanks for that, that helps a lot. The next thing to check might be
whether or not your application actually has access to the other nodes.
With that topology, and assuming all the nodes you included in your
original graph are in the 'WDC' data center, I'd be inclined to look for a
network issue
Also, what type of data were you reading/writing?
Regards,
Denise
Sent from mi iPad
> On Apr 15, 2016, at 8:29 AM, horschi wrote:
>
> Hi Jan,
>
> were you able to resolve your Problem?
>
> We are trying the same and also see a lot of WriteTimeouts:
>
Hi Jan,
were you able to resolve your Problem?
We are trying the same and also see a lot of WriteTimeouts:
WriteTimeoutException: Cassandra timeout during write query at consistency
SERIAL (2 replica were required but only 1 acknowledged the write)
How many clients were competing for a lock in
Thank you Jack.
Jean
On 14 Apr 2016, at 22:00 , Jack Krupansky
> wrote:
Normally, since 3.5 just came out, it would be wise to see if people report any
problems over the next few weeks.
But... the new tick-tock release process is