Thanks, I think it got resolved after an update.
Kind regards,
Mikhail
On Wed, Jul 15, 2015 at 2:04 PM, Sebastian Estevez <
sebastian.este...@datastax.com> wrote:
> OpsCenter 5.2 has a couple of fixes that may result in the symptoms you
> described:
> http://docs.datas
> tax.com/en/opscenter/5.2
OpsCenter 5.2 has a couple of fixes that may result in the symptoms you
described:
http://docs.datas
tax.com/en/opscenter/5.2/opsc/release_notes/opscReleaseNotes520.html
- Fixed issues with agent OOM when storing metrics for large numbers of
tables. (OPSC-5934
- Improved handling of me
On Wed, Jul 15, 2015 at 9:28 AM, Benyi Wang wrote:
> I have a small cluster with 3 nodes and installed Cassandra 2.1.2 from
> DataStax YUM repository. I knew 2.1.2 is not recommended for production.
> I'm wondering what is the root cause of the worse performance for vnode:
>
>- num_token is t
I have a small cluster with 3 nodes and installed Cassandra 2.1.2 from
DataStax YUM repository. I knew 2.1.2 is not recommended for production.
The problem I observed is:
- When I use vnode with num_token=256, the read latency is about 20ms
for 50 percentile.
- If I disable vnode, the re
On 07/15/2015 02:28 AM, Amlan Roy wrote:
Hi,
I get the following error intermittently while writing to Cassandra.
I am using version 2.1.7. Not sure how to fix the actual issue
without increasing the timeout in cassandra.yaml.
Post your data model, query, and maybe some cluster config basics
Hi,
I get the following error intermittently while writing to Cassandra. I am using
version 2.1.7. Not sure how to fix the actual issue without increasing the
timeout in cassandra.yaml.
Regards,
Amlan
java.lang.RuntimeException:
com.datastax.driver.core.exceptions.WriteTimeoutException: Cass
