[jira] [Resolved] (CASSANDRA-13821) A lot of ReadTimeoutException errors
[
https://issues.apache.org/jira/browse/CASSANDRA-13821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramiro Rioboo resolved CASSANDRA-13821.
---
Resolution: Not A Bug
> A lot of ReadTimeoutException errors
>
>
> Key: CASSANDRA-13821
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13821
> Project: Cassandra
> Issue Type: Bug
> Components: Core, CQL
> Environment: We have a Cassandra Cluster with 2 Datacenters:
> Cassandra Version: 2.2.5
> *+DC1 - OperationalDC:+*
> 3 nodes Virtual Server on VMWare.
> S.O.: Windows 2012 Server 64bits-native
> vCPU 12 Cores @ 2.5Ghz
> RAM: 16GB
> HDD: 3,6 TB Virtual Drive
> *+DC2 - AnalyticalDC:+*
> 3 nodes Virtual Server on VMWare.
> S.O.: Running on Windows 2012 Server 64bits-native
> vCPU 12 Cores @ 2.5Ghz
> RAM: 16GB
> HDD: 3,6 TB Virtual Drive
>Reporter: Ramiro Rioboo
> Labels: performance, windows
> Fix For: 2.2.5
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Our application connects directly to OperationalDC via CQL.
> During the daily operation we have a large number of WriteTimeoutException
> and ReadTimeoutException errors.
> In the logs of Cassandra we can see that the read and write timeout errors
> are also recorded with the error:
> _Java.lang.RuntimeException: java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 1 responses._
> *+Log Detail, Application Level:+*
> _22:54:22,945 [ERROR] AbstractEntityManager - Insert object
> 'Event{...}' error com.datastax.driver.core.exceptions.WriteTimeoutException:
> Cassandra timeout during write query at consistency LOCAL_QUORUM (2 replica
> were required but only 1 acknowledged the write)_
> *+Log Detail, Cassandra Level:+*
> _EBUG [SharedPool-Worker-6] 2017-08-24 08:36:40,114 StorageProxy.java:1893 -
> Range slice failure; received 0 of 1 responses for range 1 of 1
> java.lang.RuntimeException: java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 1 responses._
> The timeout error occurs 2 seconds later because of the configuration in the
> yaml:+underlined text+
> _# How long the coordinator should wait for writes to complete
> write_request_timeout_in_ms: 2000_
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13821) A lot of ReadTimeoutException errors
[
https://issues.apache.org/jira/browse/CASSANDRA-13821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16146308#comment-16146308
]
Ramiro Rioboo commented on CASSANDRA-13821:
---
Jeff,
Good to know that. Thanks for the confirmation.
I will close the Case.
Thanks,
R.-
> A lot of ReadTimeoutException errors
>
>
> Key: CASSANDRA-13821
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13821
> Project: Cassandra
> Issue Type: Bug
> Components: Core, CQL
> Environment: We have a Cassandra Cluster with 2 Datacenters:
> Cassandra Version: 2.2.5
> *+DC1 - OperationalDC:+*
> 3 nodes Virtual Server on VMWare.
> S.O.: Windows 2012 Server 64bits-native
> vCPU 12 Cores @ 2.5Ghz
> RAM: 16GB
> HDD: 3,6 TB Virtual Drive
> *+DC2 - AnalyticalDC:+*
> 3 nodes Virtual Server on VMWare.
> S.O.: Running on Windows 2012 Server 64bits-native
> vCPU 12 Cores @ 2.5Ghz
> RAM: 16GB
> HDD: 3,6 TB Virtual Drive
>Reporter: Ramiro Rioboo
> Labels: performance, windows
> Fix For: 2.2.5
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Our application connects directly to OperationalDC via CQL.
> During the daily operation we have a large number of WriteTimeoutException
> and ReadTimeoutException errors.
> In the logs of Cassandra we can see that the read and write timeout errors
> are also recorded with the error:
> _Java.lang.RuntimeException: java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 1 responses._
> *+Log Detail, Application Level:+*
> _22:54:22,945 [ERROR] AbstractEntityManager - Insert object
> 'Event{...}' error com.datastax.driver.core.exceptions.WriteTimeoutException:
> Cassandra timeout during write query at consistency LOCAL_QUORUM (2 replica
> were required but only 1 acknowledged the write)_
> *+Log Detail, Cassandra Level:+*
> _EBUG [SharedPool-Worker-6] 2017-08-24 08:36:40,114 StorageProxy.java:1893 -
> Range slice failure; received 0 of 1 responses for range 1 of 1
> java.lang.RuntimeException: java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 1 responses._
> The timeout error occurs 2 seconds later because of the configuration in the
> yaml:+underlined text+
> _# How long the coordinator should wait for writes to complete
> write_request_timeout_in_ms: 2000_
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-13821) A lot of ReadTimeoutException errors
[
https://issues.apache.org/jira/browse/CASSANDRA-13821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramiro Rioboo updated CASSANDRA-13821:
--
Attachment: (was: operational logs.part01.rar)
> A lot of ReadTimeoutException errors
>
>
> Key: CASSANDRA-13821
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13821
> Project: Cassandra
> Issue Type: Bug
> Components: Core, CQL
> Environment: We have a Cassandra Cluster with 2 Datacenters:
> Cassandra Version: 2.2.5
> *+DC1 - OperationalDC:+*
> 3 nodes Virtual Server on VMWare.
> S.O.: Windows 2012 Server 64bits-native
> vCPU 12 Cores @ 2.5Ghz
> RAM: 16GB
> HDD: 3,6 TB Virtual Drive
> *+DC2 - AnalyticalDC:+*
> 3 nodes Virtual Server on VMWare.
> S.O.: Running on Windows 2012 Server 64bits-native
> vCPU 12 Cores @ 2.5Ghz
> RAM: 16GB
> HDD: 3,6 TB Virtual Drive
>Reporter: Ramiro Rioboo
> Labels: performance, windows
> Fix For: 2.2.5
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Our application connects directly to OperationalDC via CQL.
> During the daily operation we have a large number of WriteTimeoutException
> and ReadTimeoutException errors.
> In the logs of Cassandra we can see that the read and write timeout errors
> are also recorded with the error:
> _Java.lang.RuntimeException: java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 1 responses._
> *+Log Detail, Application Level:+*
> _22:54:22,945 [ERROR] AbstractEntityManager - Insert object
> 'Event{...}' error com.datastax.driver.core.exceptions.WriteTimeoutException:
> Cassandra timeout during write query at consistency LOCAL_QUORUM (2 replica
> were required but only 1 acknowledged the write)_
> *+Log Detail, Cassandra Level:+*
> _EBUG [SharedPool-Worker-6] 2017-08-24 08:36:40,114 StorageProxy.java:1893 -
> Range slice failure; received 0 of 1 responses for range 1 of 1
> java.lang.RuntimeException: java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 1 responses._
> The timeout error occurs 2 seconds later because of the configuration in the
> yaml:+underlined text+
> _# How long the coordinator should wait for writes to complete
> write_request_timeout_in_ms: 2000_
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-13821) A lot of ReadTimeoutException errors
[
https://issues.apache.org/jira/browse/CASSANDRA-13821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramiro Rioboo updated CASSANDRA-13821:
--
Attachment: (was: CCGWEAPP05_cassandra.yaml)
> A lot of ReadTimeoutException errors
>
>
> Key: CASSANDRA-13821
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13821
> Project: Cassandra
> Issue Type: Bug
> Components: Core, CQL
> Environment: We have a Cassandra Cluster with 2 Datacenters:
> Cassandra Version: 2.2.5
> *+DC1 - OperationalDC:+*
> 3 nodes Virtual Server on VMWare.
> S.O.: Windows 2012 Server 64bits-native
> vCPU 12 Cores @ 2.5Ghz
> RAM: 16GB
> HDD: 3,6 TB Virtual Drive
> *+DC2 - AnalyticalDC:+*
> 3 nodes Virtual Server on VMWare.
> S.O.: Running on Windows 2012 Server 64bits-native
> vCPU 12 Cores @ 2.5Ghz
> RAM: 16GB
> HDD: 3,6 TB Virtual Drive
>Reporter: Ramiro Rioboo
> Labels: performance, windows
> Fix For: 2.2.5
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Our application connects directly to OperationalDC via CQL.
> During the daily operation we have a large number of WriteTimeoutException
> and ReadTimeoutException errors.
> In the logs of Cassandra we can see that the read and write timeout errors
> are also recorded with the error:
> _Java.lang.RuntimeException: java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 1 responses._
> *+Log Detail, Application Level:+*
> _22:54:22,945 [ERROR] AbstractEntityManager - Insert object
> 'Event{...}' error com.datastax.driver.core.exceptions.WriteTimeoutException:
> Cassandra timeout during write query at consistency LOCAL_QUORUM (2 replica
> were required but only 1 acknowledged the write)_
> *+Log Detail, Cassandra Level:+*
> _EBUG [SharedPool-Worker-6] 2017-08-24 08:36:40,114 StorageProxy.java:1893 -
> Range slice failure; received 0 of 1 responses for range 1 of 1
> java.lang.RuntimeException: java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 1 responses._
> The timeout error occurs 2 seconds later because of the configuration in the
> yaml:+underlined text+
> _# How long the coordinator should wait for writes to complete
> write_request_timeout_in_ms: 2000_
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-13821) A lot of ReadTimeoutException errors
[
https://issues.apache.org/jira/browse/CASSANDRA-13821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramiro Rioboo updated CASSANDRA-13821:
--
Attachment: (was: operational logs.part03.rar)
> A lot of ReadTimeoutException errors
>
>
> Key: CASSANDRA-13821
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13821
> Project: Cassandra
> Issue Type: Bug
> Components: Core, CQL
> Environment: We have a Cassandra Cluster with 2 Datacenters:
> Cassandra Version: 2.2.5
> *+DC1 - OperationalDC:+*
> 3 nodes Virtual Server on VMWare.
> S.O.: Windows 2012 Server 64bits-native
> vCPU 12 Cores @ 2.5Ghz
> RAM: 16GB
> HDD: 3,6 TB Virtual Drive
> *+DC2 - AnalyticalDC:+*
> 3 nodes Virtual Server on VMWare.
> S.O.: Running on Windows 2012 Server 64bits-native
> vCPU 12 Cores @ 2.5Ghz
> RAM: 16GB
> HDD: 3,6 TB Virtual Drive
>Reporter: Ramiro Rioboo
> Labels: performance, windows
> Fix For: 2.2.5
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Our application connects directly to OperationalDC via CQL.
> During the daily operation we have a large number of WriteTimeoutException
> and ReadTimeoutException errors.
> In the logs of Cassandra we can see that the read and write timeout errors
> are also recorded with the error:
> _Java.lang.RuntimeException: java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 1 responses._
> *+Log Detail, Application Level:+*
> _22:54:22,945 [ERROR] AbstractEntityManager - Insert object
> 'Event{...}' error com.datastax.driver.core.exceptions.WriteTimeoutException:
> Cassandra timeout during write query at consistency LOCAL_QUORUM (2 replica
> were required but only 1 acknowledged the write)_
> *+Log Detail, Cassandra Level:+*
> _EBUG [SharedPool-Worker-6] 2017-08-24 08:36:40,114 StorageProxy.java:1893 -
> Range slice failure; received 0 of 1 responses for range 1 of 1
> java.lang.RuntimeException: java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 1 responses._
> The timeout error occurs 2 seconds later because of the configuration in the
> yaml:+underlined text+
> _# How long the coordinator should wait for writes to complete
> write_request_timeout_in_ms: 2000_
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-13821) A lot of ReadTimeoutException errors
[
https://issues.apache.org/jira/browse/CASSANDRA-13821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramiro Rioboo updated CASSANDRA-13821:
--
Attachment: (was: operational logs.part02.rar)
> A lot of ReadTimeoutException errors
>
>
> Key: CASSANDRA-13821
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13821
> Project: Cassandra
> Issue Type: Bug
> Components: Core, CQL
> Environment: We have a Cassandra Cluster with 2 Datacenters:
> Cassandra Version: 2.2.5
> *+DC1 - OperationalDC:+*
> 3 nodes Virtual Server on VMWare.
> S.O.: Windows 2012 Server 64bits-native
> vCPU 12 Cores @ 2.5Ghz
> RAM: 16GB
> HDD: 3,6 TB Virtual Drive
> *+DC2 - AnalyticalDC:+*
> 3 nodes Virtual Server on VMWare.
> S.O.: Running on Windows 2012 Server 64bits-native
> vCPU 12 Cores @ 2.5Ghz
> RAM: 16GB
> HDD: 3,6 TB Virtual Drive
>Reporter: Ramiro Rioboo
> Labels: performance, windows
> Fix For: 2.2.5
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Our application connects directly to OperationalDC via CQL.
> During the daily operation we have a large number of WriteTimeoutException
> and ReadTimeoutException errors.
> In the logs of Cassandra we can see that the read and write timeout errors
> are also recorded with the error:
> _Java.lang.RuntimeException: java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 1 responses._
> *+Log Detail, Application Level:+*
> _22:54:22,945 [ERROR] AbstractEntityManager - Insert object
> 'Event{...}' error com.datastax.driver.core.exceptions.WriteTimeoutException:
> Cassandra timeout during write query at consistency LOCAL_QUORUM (2 replica
> were required but only 1 acknowledged the write)_
> *+Log Detail, Cassandra Level:+*
> _EBUG [SharedPool-Worker-6] 2017-08-24 08:36:40,114 StorageProxy.java:1893 -
> Range slice failure; received 0 of 1 responses for range 1 of 1
> java.lang.RuntimeException: java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 1 responses._
> The timeout error occurs 2 seconds later because of the configuration in the
> yaml:+underlined text+
> _# How long the coordinator should wait for writes to complete
> write_request_timeout_in_ms: 2000_
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-13821) A lot of ReadTimeoutException errors
[
https://issues.apache.org/jira/browse/CASSANDRA-13821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramiro Rioboo updated CASSANDRA-13821:
--
Attachment: (was: CCGWEAPP04_cassandra.yaml)
> A lot of ReadTimeoutException errors
>
>
> Key: CASSANDRA-13821
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13821
> Project: Cassandra
> Issue Type: Bug
> Components: Core, CQL
> Environment: We have a Cassandra Cluster with 2 Datacenters:
> Cassandra Version: 2.2.5
> *+DC1 - OperationalDC:+*
> 3 nodes Virtual Server on VMWare.
> S.O.: Windows 2012 Server 64bits-native
> vCPU 12 Cores @ 2.5Ghz
> RAM: 16GB
> HDD: 3,6 TB Virtual Drive
> *+DC2 - AnalyticalDC:+*
> 3 nodes Virtual Server on VMWare.
> S.O.: Running on Windows 2012 Server 64bits-native
> vCPU 12 Cores @ 2.5Ghz
> RAM: 16GB
> HDD: 3,6 TB Virtual Drive
>Reporter: Ramiro Rioboo
> Labels: performance, windows
> Fix For: 2.2.5
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Our application connects directly to OperationalDC via CQL.
> During the daily operation we have a large number of WriteTimeoutException
> and ReadTimeoutException errors.
> In the logs of Cassandra we can see that the read and write timeout errors
> are also recorded with the error:
> _Java.lang.RuntimeException: java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 1 responses._
> *+Log Detail, Application Level:+*
> _22:54:22,945 [ERROR] AbstractEntityManager - Insert object
> 'Event{...}' error com.datastax.driver.core.exceptions.WriteTimeoutException:
> Cassandra timeout during write query at consistency LOCAL_QUORUM (2 replica
> were required but only 1 acknowledged the write)_
> *+Log Detail, Cassandra Level:+*
> _EBUG [SharedPool-Worker-6] 2017-08-24 08:36:40,114 StorageProxy.java:1893 -
> Range slice failure; received 0 of 1 responses for range 1 of 1
> java.lang.RuntimeException: java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 1 responses._
> The timeout error occurs 2 seconds later because of the configuration in the
> yaml:+underlined text+
> _# How long the coordinator should wait for writes to complete
> write_request_timeout_in_ms: 2000_
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-13821) A lot of ReadTimeoutException errors
[
https://issues.apache.org/jira/browse/CASSANDRA-13821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramiro Rioboo updated CASSANDRA-13821:
--
Attachment: (was: CCGWEAPP03_cassandra.yaml)
> A lot of ReadTimeoutException errors
>
>
> Key: CASSANDRA-13821
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13821
> Project: Cassandra
> Issue Type: Bug
> Components: Core, CQL
> Environment: We have a Cassandra Cluster with 2 Datacenters:
> Cassandra Version: 2.2.5
> *+DC1 - OperationalDC:+*
> 3 nodes Virtual Server on VMWare.
> S.O.: Windows 2012 Server 64bits-native
> vCPU 12 Cores @ 2.5Ghz
> RAM: 16GB
> HDD: 3,6 TB Virtual Drive
> *+DC2 - AnalyticalDC:+*
> 3 nodes Virtual Server on VMWare.
> S.O.: Running on Windows 2012 Server 64bits-native
> vCPU 12 Cores @ 2.5Ghz
> RAM: 16GB
> HDD: 3,6 TB Virtual Drive
>Reporter: Ramiro Rioboo
> Labels: performance, windows
> Fix For: 2.2.5
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Our application connects directly to OperationalDC via CQL.
> During the daily operation we have a large number of WriteTimeoutException
> and ReadTimeoutException errors.
> In the logs of Cassandra we can see that the read and write timeout errors
> are also recorded with the error:
> _Java.lang.RuntimeException: java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 1 responses._
> *+Log Detail, Application Level:+*
> _22:54:22,945 [ERROR] AbstractEntityManager - Insert object
> 'Event{...}' error com.datastax.driver.core.exceptions.WriteTimeoutException:
> Cassandra timeout during write query at consistency LOCAL_QUORUM (2 replica
> were required but only 1 acknowledged the write)_
> *+Log Detail, Cassandra Level:+*
> _EBUG [SharedPool-Worker-6] 2017-08-24 08:36:40,114 StorageProxy.java:1893 -
> Range slice failure; received 0 of 1 responses for range 1 of 1
> java.lang.RuntimeException: java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 1 responses._
> The timeout error occurs 2 seconds later because of the configuration in the
> yaml:+underlined text+
> _# How long the coordinator should wait for writes to complete
> write_request_timeout_in_ms: 2000_
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13821) A lot of ReadTimeoutException errors
[
https://issues.apache.org/jira/browse/CASSANDRA-13821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16146294#comment-16146294
]
Ramiro Rioboo commented on CASSANDRA-13821:
---
Hello Jeff,
I did not find a qualifying option: environmental / tuning / network.
Could you please tell me which Type should I apply?
Thanks,
R.-
> A lot of ReadTimeoutException errors
>
>
> Key: CASSANDRA-13821
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13821
> Project: Cassandra
> Issue Type: Bug
> Components: Core, CQL
> Environment: We have a Cassandra Cluster with 2 Datacenters:
> Cassandra Version: 2.2.5
> *+DC1 - OperationalDC:+*
> 3 nodes Virtual Server on VMWare.
> S.O.: Windows 2012 Server 64bits-native
> vCPU 12 Cores @ 2.5Ghz
> RAM: 16GB
> HDD: 3,6 TB Virtual Drive
> *+DC2 - AnalyticalDC:+*
> 3 nodes Virtual Server on VMWare.
> S.O.: Running on Windows 2012 Server 64bits-native
> vCPU 12 Cores @ 2.5Ghz
> RAM: 16GB
> HDD: 3,6 TB Virtual Drive
>Reporter: Ramiro Rioboo
> Labels: performance, windows
> Fix For: 2.2.5
>
> Attachments: CCGWEAPP03_cassandra.yaml, CCGWEAPP04_cassandra.yaml,
> CCGWEAPP05_cassandra.yaml, operational logs.part01.rar, operational
> logs.part02.rar, operational logs.part03.rar
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Our application connects directly to OperationalDC via CQL.
> During the daily operation we have a large number of WriteTimeoutException
> and ReadTimeoutException errors.
> In the logs of Cassandra we can see that the read and write timeout errors
> are also recorded with the error:
> _Java.lang.RuntimeException: java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 1 responses._
> *+Log Detail, Application Level:+*
> _22:54:22,945 [ERROR] AbstractEntityManager - Insert object
> 'Event{...}' error com.datastax.driver.core.exceptions.WriteTimeoutException:
> Cassandra timeout during write query at consistency LOCAL_QUORUM (2 replica
> were required but only 1 acknowledged the write)_
> *+Log Detail, Cassandra Level:+*
> _EBUG [SharedPool-Worker-6] 2017-08-24 08:36:40,114 StorageProxy.java:1893 -
> Range slice failure; received 0 of 1 responses for range 1 of 1
> java.lang.RuntimeException: java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 1 responses._
> The timeout error occurs 2 seconds later because of the configuration in the
> yaml:+underlined text+
> _# How long the coordinator should wait for writes to complete
> write_request_timeout_in_ms: 2000_
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-13821) A lot of ReadTimeoutException errors
Ramiro Rioboo created CASSANDRA-13821:
-
Summary: A lot of ReadTimeoutException errors
Key: CASSANDRA-13821
URL: https://issues.apache.org/jira/browse/CASSANDRA-13821
Project: Cassandra
Issue Type: Bug
Components: Core, CQL
Environment: We have a Cassandra Cluster with 2 Datacenters:
Cassandra Version: 2.2.5
*+DC1 - OperationalDC:+*
3 nodes Virtual Server on VMWare.
S.O.: Windows 2012 Server 64bits-native
vCPU 12 Cores @ 2.5Ghz
RAM: 16GB
HDD: 3,6 TB Virtual Drive
*+DC2 - AnalyticalDC:+*
3 nodes Virtual Server on VMWare.
S.O.: Running on Windows 2012 Server 64bits-native
vCPU 12 Cores @ 2.5Ghz
RAM: 16GB
HDD: 3,6 TB Virtual Drive
Reporter: Ramiro Rioboo
Fix For: 2.2.5
Attachments: CCGWEAPP03_cassandra.yaml, CCGWEAPP04_cassandra.yaml,
CCGWEAPP05_cassandra.yaml, operational logs.part01.rar, operational
logs.part02.rar, operational logs.part03.rar
Our application connects directly to OperationalDC via CQL.
During the daily operation we have a large number of WriteTimeoutException and
ReadTimeoutException errors.
In the logs of Cassandra we can see that the read and write timeout errors are
also recorded with the error:
_Java.lang.RuntimeException: java.lang.RuntimeException:
org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
received only 1 responses._
*+Log Detail, Application Level:+*
_22:54:22,945 [ERROR] AbstractEntityManager - Insert object
'Event{...}' error com.datastax.driver.core.exceptions.WriteTimeoutException:
Cassandra timeout during write query at consistency LOCAL_QUORUM (2 replica
were required but only 1 acknowledged the write)_
*+Log Detail, Cassandra Level:+*
_EBUG [SharedPool-Worker-6] 2017-08-24 08:36:40,114 StorageProxy.java:1893 -
Range slice failure; received 0 of 1 responses for range 1 of 1
java.lang.RuntimeException: java.lang.RuntimeException:
org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
received only 1 responses._
The timeout error occurs 2 seconds later because of the configuration in the
yaml:+underlined text+
_# How long the coordinator should wait for writes to complete
write_request_timeout_in_ms: 2000_
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
