[jira] [Commented] (CASSANDRA-10007) Repeated rows in paged result
[ https://issues.apache.org/jira/browse/CASSANDRA-10007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703413#comment-14703413 ] Steve Wang commented on CASSANDRA-10007: Hi Benjamin! Yes, I'm still able to reproduce this error. What I do is start a 3 node cluster in CCM and then run the paging-test.py script that Adam attached in this ticket. The first two values are as expected, but the next few values, which should be 100, oscillate between 104 and 103. Repeated rows in paged result - Key: CASSANDRA-10007 URL: https://issues.apache.org/jira/browse/CASSANDRA-10007 Project: Cassandra Issue Type: Bug Components: Core Reporter: Adam Holmberg Assignee: Benjamin Lerer Labels: client-impacting Fix For: 3.x Attachments: paging-test.py We noticed an anomaly in paged results while testing against 3.0.0-alpha1. It seems that unbounded selects can return rows repeated at page boundaries. Furthermore, the number of repeated rows seems to dither in count across consecutive runs of the same query. Does not reproduce on 2.2.0 and earlier. I also noted that this behavior only manifests on multi-node clusters. The attached script shows this behavior when run against 3.0.0-alpha1. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CASSANDRA-7436) Dtest for tracking metrics regressions
[ https://issues.apache.org/jira/browse/CASSANDRA-7436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Wang resolved CASSANDRA-7436. --- Resolution: Implemented Reviewer: Philip Thompson Fix Version/s: 2.1.x 3.x Reproduced In: 3.0 alpha 1, 2.2.0 Created jmxmetrics_test Dtest for tracking metrics regressions -- Key: CASSANDRA-7436 URL: https://issues.apache.org/jira/browse/CASSANDRA-7436 Project: Cassandra Issue Type: Test Reporter: Ryan McGuire Assignee: Steve Wang Fix For: 3.x, 2.1.x We should create a dtest that runs a small load test and collects a bunch of the JMX metrics and introduce assertions to ensure they are roughly the same every time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-7436) Dtest for tracking metrics regressions
[ https://issues.apache.org/jira/browse/CASSANDRA-7436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14702013#comment-14702013 ] Steve Wang commented on CASSANDRA-7436: --- Created jmxmetrics_test, which takes JMX metrics and tests whether they work as expected. Unfortunately, I'm not too familiar as to how each value should change, so I only judged their expected change by tracking the change in values a couple times myself. Dtest for tracking metrics regressions -- Key: CASSANDRA-7436 URL: https://issues.apache.org/jira/browse/CASSANDRA-7436 Project: Cassandra Issue Type: Test Reporter: Ryan McGuire Assignee: Steve Wang We should create a dtest that runs a small load test and collects a bunch of the JMX metrics and introduce assertions to ensure they are roughly the same every time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-10007) Repeated rows in paged result
[ https://issues.apache.org/jira/browse/CASSANDRA-10007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14662630#comment-14662630 ] Steve Wang commented on CASSANDRA-10007: Seems to work fine in dtest, as Adam and I both found to be true. The problem seems to be when the cluster is running on more than one node. There's a direct correlation between the number of nodes and the number of rows returned. In addition, there's an inverse relation between the fetch_size and the number_of_rows returned. For example, with: 5 nodes, fetch_size = 3 i get values from select* from test.test oscillating between 112 and 113, when the result should be 100. In addition, the error only seems to occur when there isn't a limit. Repeated rows in paged result - Key: CASSANDRA-10007 URL: https://issues.apache.org/jira/browse/CASSANDRA-10007 Project: Cassandra Issue Type: Bug Components: Core Reporter: Adam Holmberg Assignee: Benjamin Lerer Labels: client-impacting Fix For: 3.x Attachments: paging-test.py We noticed an anomaly in paged results while testing against 3.0.0-alpha1. It seems that unbounded selects can return rows repeated at page boundaries. Furthermore, the number of repeated rows seems to dither in count across consecutive runs of the same query. Does not reproduce on 2.2.0 and earlier. I also noted that this behavior only manifests on multi-node clusters. The attached script shows this behavior when run against 3.0.0-alpha1. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-9971) Static variables with small page sizes
[ https://issues.apache.org/jira/browse/CASSANDRA-9971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Wang updated CASSANDRA-9971: -- Fix Version/s: (was: 2.2.x) Static variables with small page sizes -- Key: CASSANDRA-9971 URL: https://issues.apache.org/jira/browse/CASSANDRA-9971 Project: Cassandra Issue Type: Bug Components: Tests Environment: Local Reporter: Steve Wang Fix For: 3.x Attachments: static_paging_test.py Selecting static variables with small page sizes causes them to display as None. With large page sizes and non-static variables, test still pass. Works fine in 2.1.x. Not sure if it runs in 2.2.x, Run the test below to see error. Remove the list on line 21 to see what's actually erroring. Related to 8502. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-9971) Static variables with small page sizes
[ https://issues.apache.org/jira/browse/CASSANDRA-9971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Wang updated CASSANDRA-9971: -- Description: Selecting static variables with small page sizes causes them to display as None. With large page sizes and non-static variables, test still pass. Works fine in 2.1.x. Not sure if it runs in 2.2.x (I can't seem to run C* version 2.2.x). Run the test below to see error. Remove the list on line 21 to see what's actually erroring. Related to 8502. was: Selecting static variables with small page sizes causes them to display as None. With large page sizes and non-static variables, test still pass. Works fine in 2.1.x. Not sure if it runs in 2.2.x, Run the test below to see error. Remove the list on line 21 to see what's actually erroring. Related to 8502. Static variables with small page sizes -- Key: CASSANDRA-9971 URL: https://issues.apache.org/jira/browse/CASSANDRA-9971 Project: Cassandra Issue Type: Bug Components: Tests Environment: Local Reporter: Steve Wang Fix For: 3.x Attachments: static_paging_test.py Selecting static variables with small page sizes causes them to display as None. With large page sizes and non-static variables, test still pass. Works fine in 2.1.x. Not sure if it runs in 2.2.x (I can't seem to run C* version 2.2.x). Run the test below to see error. Remove the list on line 21 to see what's actually erroring. Related to 8502. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-9971) Static variables with small page sizes
[ https://issues.apache.org/jira/browse/CASSANDRA-9971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Wang updated CASSANDRA-9971: -- Description: Selecting static variables with small page sizes causes them to display as None. With large page sizes and non-static variables, test still pass. Works fine in 2.1.x. Not sure if it runs in 2.2.x, Run the test below to see error. Remove the list on line 21 to see what's actually erroring. Related to 8502. was: Selecting static variables with small page sizes causes them to display as None. With large page sizes and non-static variables, test still pass. Works fine in 2.1.x. Run the test below to see error. Remove the list on line 21 to see what's actually erroring. Related to 8502. Static variables with small page sizes -- Key: CASSANDRA-9971 URL: https://issues.apache.org/jira/browse/CASSANDRA-9971 Project: Cassandra Issue Type: Bug Components: Tests Environment: Local Reporter: Steve Wang Fix For: 3.x Attachments: static_paging_test.py Selecting static variables with small page sizes causes them to display as None. With large page sizes and non-static variables, test still pass. Works fine in 2.1.x. Not sure if it runs in 2.2.x, Run the test below to see error. Remove the list on line 21 to see what's actually erroring. Related to 8502. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CASSANDRA-9971) Static variables with small page sizes
Steve Wang created CASSANDRA-9971: - Summary: Static variables with small page sizes Key: CASSANDRA-9971 URL: https://issues.apache.org/jira/browse/CASSANDRA-9971 Project: Cassandra Issue Type: Bug Components: Tests Environment: Local Reporter: Steve Wang Fix For: 3.x, 2.2.x Attachments: static_paging_test.py Selecting static variables with small page sizes causes them to display as None. With large page sizes and non-static variables, test still pass. Works fine in 2.1.x. Run the test below to see error. Remove the list on line 21 to see what's actually erroring. Related to 8502. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-9807) CQL Insert
[ https://issues.apache.org/jira/browse/CASSANDRA-9807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14628553#comment-14628553 ] Steve Wang commented on CASSANDRA-9807: --- My apologies, should have documented a bit more. The purpose of this test was just to detail what the logs output in response to each execute statement. I think there's an issue, because when I remove Insert from the test that I attached, it doesn't output the message in the logs. I spoke with Shawn Kumar, and he received the same message when running read_repair_test. CQL Insert --- Key: CASSANDRA-9807 URL: https://issues.apache.org/jira/browse/CASSANDRA-9807 Project: Cassandra Issue Type: Bug Components: Tests Environment: local environment Reporter: Steve Wang Priority: Minor Fix For: 2.1.x Attachments: play_test.py Executing an INSERT statement doesn't seem to go through. Results in log message: WARN [SharedPool-Worker-2] 2015-07-14 11:25:24,311 FBUtilities.java:345 - Trigger directory doesn't exist, please create it and try again. Replicated this error in read_repair_test.py and a little test I wrote up myself which I've attached below. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CASSANDRA-9807) CQL Insert
Steve Wang created CASSANDRA-9807: - Summary: CQL Insert Key: CASSANDRA-9807 URL: https://issues.apache.org/jira/browse/CASSANDRA-9807 Project: Cassandra Issue Type: Bug Components: Tests Environment: local environment Reporter: Steve Wang Priority: Minor Fix For: 2.1.x Attachments: play_test.py Executing an INSERT statement doesn't seem to go through. Results in log message: WARN [SharedPool-Worker-2] 2015-07-14 11:25:24,311 FBUtilities.java:345 - Trigger directory doesn't exist, please create it and try again. Replicated this error in read_repair_test.py and a little test I wrote up myself which I've attached below. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CASSANDRA-5322) Make dtest logging more granular
[ https://issues.apache.org/jira/browse/CASSANDRA-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Wang resolved CASSANDRA-5322. --- Resolution: Fixed Fix Version/s: (was: 3.x) 2.2.x 2.1.x Reviewer: Philip Thompson Reproduced In: 2.1.5 Modified ccmlib/cluster.py, ccmlib/common.py, and cassandra-dtest/dtest.py. I modified the dtest environment variables DEBUG and TRACE so that they could not only accept true/yes and false/no, but also names of C* classes (can add multiple by separating them with a colon). I did this using three functions: var_debug, var_trace, and modify_log. The first two change the log_level of the cluster for a specific class (If it's that is the case), and modify_log calls all the potential changes to the log_level's all at once. In cluster.py, I modified the add and set_log_level functions, and also added two global arrays, _debug and _trace. The two global variables serve to keep track of what classes have the respective log levels. In the set_log_level function, we check if there is a class_name being inputted, and if there is, we make sure it's not already being called. We then append the class to the respective global array, and then change the log_level on the node level. In the add function, I added a feature that whenever a node is added, it'll automatically take in the settings already set forth for class logging levels. Finally, in common.py, I modified the replaces_or_add_into_file_tail function. Before, all additional modifications would be written on the very last line of the file after the closing tag, which means it wasn't being read. This includes modifications to the log level. I changed it so that it would be added before the closing tag. Make dtest logging more granular - Key: CASSANDRA-5322 URL: https://issues.apache.org/jira/browse/CASSANDRA-5322 Project: Cassandra Issue Type: Test Reporter: Ryan McGuire Assignee: Steve Wang Fix For: 2.1.x, 2.2.x From Brandon: We need a way (might need to go in ccm, I haven't looked) to just set one class to DEBUG or TRACE, like we'd do in conf/log4-server.properties but with an env var preferably, so I can control it via buildbot, since it's better at reproducing some issues than I am sometimes, but I don't want to run the full hammer debug all the time. Also, a way to set Tester.allow_log_errors to false via an env var, since sometimes there's an error there that takes a while to fix but is cosmetic, and in the meantime I want to catch new failures so we don't fall behind. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
