You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (Created) (JIRA)" <ji...@apache.org> on 2012/02/03 17:27:53 UTC
[jira] [Created] (DERBY-5599) readlocks.sql fails with extra locks.
Possibly Automatic Index statistics kicking off during test
readlocks.sql fails with extra locks. Possibly Automatic Index statistics kicking off during test
--------------------------------------------------------------------------------------------------
Key: DERBY-5599
URL: https://issues.apache.org/jira/browse/DERBY-5599
Project: Derby
Issue Type: Bug
Reporter: Kathey Marsden
I saw this failure for the Feb 1 run at:
http://people.apache.org/~myrnavl/derby_test_results/v10_8/linux/testlog/ibm15/1239442-derbyall_diff.txt
I think it is likely the index statistics update kicking in during the test. I am thinking should not be disabled for the derbyall store tests as having it kick in can cause upredictable reporting of locks pages used, etc.
*** Start: readlocks jdk1.5.0 storeall:storemore 2012-02-01 21:11:01 ***
11113a11114
> APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
11122a11124
> APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
11131a11134
> APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
11138a11142
> APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
Test Failed.
*** End: readlocks jdk1.5.0 storeall:storemore 2012-02-01 21:13:31 ***
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DERBY-5599) readlocks.sql fails with extra locks.
Posted by "Mike Matrigali (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali updated DERBY-5599:
----------------------------------
Issue & fix info: High Value Fix
Urgency: Normal
Labels: derby_triage10_9 (was: )
> readlocks.sql fails with extra locks.
> -------------------------------------
>
> Key: DERBY-5599
> URL: https://issues.apache.org/jira/browse/DERBY-5599
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.8.2.3
> Reporter: Kathey Marsden
> Assignee: Mike Matrigali
> Labels: derby_triage10_9
>
> I saw this failure for the Feb 1 run at:
> http://people.apache.org/~myrnavl/derby_test_results/v10_8/linux/testlog/ibm15/1239442-derbyall_diff.txt
> I think it is likely the index statistics update kicking in during the test. I am thinking should not be disabled for the derbyall store tests as having it kick in can cause upredictable reporting of locks pages used, etc.
> *** Start: readlocks jdk1.5.0 storeall:storemore 2012-02-01 21:11:01 ***
> 11113a11114
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> 11122a11124
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> 11131a11134
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> 11138a11142
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> Test Failed.
> *** End: readlocks jdk1.5.0 storeall:storemore 2012-02-01 21:13:31 ***
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DERBY-5599) readlocks.sql fails with extra
locks.
Posted by "Mike Matrigali (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali resolved DERBY-5599.
-----------------------------------
Resolution: Fixed
Fix Version/s: 10.9.0.0
10.8.2.3
10.7.1.4
10.6.2.2
10.5.3.2
> readlocks.sql fails with extra locks.
> -------------------------------------
>
> Key: DERBY-5599
> URL: https://issues.apache.org/jira/browse/DERBY-5599
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.8.2.3
> Reporter: Kathey Marsden
> Assignee: Mike Matrigali
> Labels: derby_triage10_9
> Fix For: 10.5.3.2, 10.6.2.2, 10.7.1.4, 10.8.2.3, 10.9.0.0
>
>
> I saw this failure for the Feb 1 run at:
> http://people.apache.org/~myrnavl/derby_test_results/v10_8/linux/testlog/ibm15/1239442-derbyall_diff.txt
> I think it is likely the index statistics update kicking in during the test. I am thinking should not be disabled for the derbyall store tests as having it kick in can cause upredictable reporting of locks pages used, etc.
> *** Start: readlocks jdk1.5.0 storeall:storemore 2012-02-01 21:11:01 ***
> 11113a11114
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> 11122a11124
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> 11131a11134
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> 11138a11142
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> Test Failed.
> *** End: readlocks jdk1.5.0 storeall:storemore 2012-02-01 21:13:31 ***
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DERBY-5599) readlocks.sql fails with extra locks.
Posted by "Kathey Marsden (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-5599:
----------------------------------
Affects Version/s: 10.8.2.3
> readlocks.sql fails with extra locks.
> -------------------------------------
>
> Key: DERBY-5599
> URL: https://issues.apache.org/jira/browse/DERBY-5599
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.8.2.3
> Reporter: Kathey Marsden
> Assignee: Mike Matrigali
>
> I saw this failure for the Feb 1 run at:
> http://people.apache.org/~myrnavl/derby_test_results/v10_8/linux/testlog/ibm15/1239442-derbyall_diff.txt
> I think it is likely the index statistics update kicking in during the test. I am thinking should not be disabled for the derbyall store tests as having it kick in can cause upredictable reporting of locks pages used, etc.
> *** Start: readlocks jdk1.5.0 storeall:storemore 2012-02-01 21:11:01 ***
> 11113a11114
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> 11122a11124
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> 11131a11134
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> 11138a11142
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> Test Failed.
> *** End: readlocks jdk1.5.0 storeall:storemore 2012-02-01 21:13:31 ***
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DERBY-5599) readlocks.sql fails with extra locks.
Posted by "Kathey Marsden (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-5599:
----------------------------------
Component/s: Test
Summary: readlocks.sql fails with extra locks. (was: readlocks.sql fails with extra locks. Possibly Automatic Index statistics kicking off during test)
Changing component to test and adjusting title to remove statistics. Not likely the cause after all.
> readlocks.sql fails with extra locks.
> -------------------------------------
>
> Key: DERBY-5599
> URL: https://issues.apache.org/jira/browse/DERBY-5599
> Project: Derby
> Issue Type: Bug
> Components: Test
> Reporter: Kathey Marsden
> Assignee: Mike Matrigali
>
> I saw this failure for the Feb 1 run at:
> http://people.apache.org/~myrnavl/derby_test_results/v10_8/linux/testlog/ibm15/1239442-derbyall_diff.txt
> I think it is likely the index statistics update kicking in during the test. I am thinking should not be disabled for the derbyall store tests as having it kick in can cause upredictable reporting of locks pages used, etc.
> *** Start: readlocks jdk1.5.0 storeall:storemore 2012-02-01 21:11:01 ***
> 11113a11114
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> 11122a11124
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> 11131a11134
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> 11138a11142
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> Test Failed.
> *** End: readlocks jdk1.5.0 storeall:storemore 2012-02-01 21:13:31 ***
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5599) readlocks.sql fails with extra
locks.
Posted by "Mike Matrigali (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212795#comment-13212795 ]
Mike Matrigali commented on DERBY-5599:
---------------------------------------
Added wait for post commit at appropriate spots after a commit following transaction with deletes. This should
limit the interaction of post commit background work with locks being looked for by the test.
checked into trunk, 10.8, 10.7, 10.6, and 10.5 branch. It can be backported more if anyone is interested.
> readlocks.sql fails with extra locks.
> -------------------------------------
>
> Key: DERBY-5599
> URL: https://issues.apache.org/jira/browse/DERBY-5599
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.8.2.3
> Reporter: Kathey Marsden
> Assignee: Mike Matrigali
> Labels: derby_triage10_9
> Fix For: 10.5.3.2, 10.6.2.2, 10.7.1.4, 10.8.2.3, 10.9.0.0
>
>
> I saw this failure for the Feb 1 run at:
> http://people.apache.org/~myrnavl/derby_test_results/v10_8/linux/testlog/ibm15/1239442-derbyall_diff.txt
> I think it is likely the index statistics update kicking in during the test. I am thinking should not be disabled for the derbyall store tests as having it kick in can cause upredictable reporting of locks pages used, etc.
> *** Start: readlocks jdk1.5.0 storeall:storemore 2012-02-01 21:11:01 ***
> 11113a11114
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> 11122a11124
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> 11131a11134
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> 11138a11142
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> Test Failed.
> *** End: readlocks jdk1.5.0 storeall:storemore 2012-02-01 21:13:31 ***
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (DERBY-5599) readlocks.sql fails with extra
locks. Possibly Automatic Index statistics kicking off during test
Posted by "Mike Matrigali (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali reassigned DERBY-5599:
-------------------------------------
Assignee: Mike Matrigali
> readlocks.sql fails with extra locks. Possibly Automatic Index statistics kicking off during test
> --------------------------------------------------------------------------------------------------
>
> Key: DERBY-5599
> URL: https://issues.apache.org/jira/browse/DERBY-5599
> Project: Derby
> Issue Type: Bug
> Reporter: Kathey Marsden
> Assignee: Mike Matrigali
>
> I saw this failure for the Feb 1 run at:
> http://people.apache.org/~myrnavl/derby_test_results/v10_8/linux/testlog/ibm15/1239442-derbyall_diff.txt
> I think it is likely the index statistics update kicking in during the test. I am thinking should not be disabled for the derbyall store tests as having it kick in can cause upredictable reporting of locks pages used, etc.
> *** Start: readlocks jdk1.5.0 storeall:storemore 2012-02-01 21:11:01 ***
> 11113a11114
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> 11122a11124
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> 11131a11134
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> 11138a11142
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> Test Failed.
> *** End: readlocks jdk1.5.0 storeall:storemore 2012-02-01 21:13:31 ***
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5599) readlocks.sql fails with extra
locks. Possibly Automatic Index statistics kicking off during test
Posted by "Kristian Waagan (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201159#comment-13201159 ]
Kristian Waagan commented on DERBY-5599:
----------------------------------------
I verified that the istat feature isn't triggered on my system. Can you ckeck that it is running on the system where the test fails?
The easiest way to do do that is to add -DtestSpecialProps=derby.storage.indexStats.log=true^derby.storage.indexStats.debug.trace=true and run the test.
Note especially the line logged on shutdown:
Mon Feb 06 09:44:31 GMT+01:00 2012 Thread[main,5,main] {istat} stopping daemon, active=false, work/age=0/52180 [q/p/s=0/0/0,err:k/u/c=0/0/0,rej:f/d/o=0/0/0]
I did tail -f readlocks/derby.log | grep "{istat}" since the log is deleted when the run is successful.
Further, the istat deamon will only run if the following default requirements are fulfilled:
o statistics are created only when the table exceeds the minimum row threshold (250 rows)
o statistics are updated only when the row difference between the two estimates exceeds 1000 rows
o statistics are updated only when the ln difference between the two estimates exceeds 1.0.
Since the statistics are index statistics there must be an index on the table, and finally a statement involving an index must be prepared (i.e select * from t where indexed_col = ?).
> readlocks.sql fails with extra locks. Possibly Automatic Index statistics kicking off during test
> --------------------------------------------------------------------------------------------------
>
> Key: DERBY-5599
> URL: https://issues.apache.org/jira/browse/DERBY-5599
> Project: Derby
> Issue Type: Bug
> Reporter: Kathey Marsden
>
> I saw this failure for the Feb 1 run at:
> http://people.apache.org/~myrnavl/derby_test_results/v10_8/linux/testlog/ibm15/1239442-derbyall_diff.txt
> I think it is likely the index statistics update kicking in during the test. I am thinking should not be disabled for the derbyall store tests as having it kick in can cause upredictable reporting of locks pages used, etc.
> *** Start: readlocks jdk1.5.0 storeall:storemore 2012-02-01 21:11:01 ***
> 11113a11114
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> 11122a11124
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> 11131a11134
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> 11138a11142
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> Test Failed.
> *** End: readlocks jdk1.5.0 storeall:storemore 2012-02-01 21:13:31 ***
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5599) readlocks.sql fails with extra
locks. Possibly Automatic Index statistics kicking off during test
Posted by "Knut Anders Hatlen (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202360#comment-13202360 ]
Knut Anders Hatlen commented on DERBY-5599:
-------------------------------------------
Similar failures were also reported before istat was introduced: DERBY-2947
> readlocks.sql fails with extra locks. Possibly Automatic Index statistics kicking off during test
> --------------------------------------------------------------------------------------------------
>
> Key: DERBY-5599
> URL: https://issues.apache.org/jira/browse/DERBY-5599
> Project: Derby
> Issue Type: Bug
> Reporter: Kathey Marsden
>
> I saw this failure for the Feb 1 run at:
> http://people.apache.org/~myrnavl/derby_test_results/v10_8/linux/testlog/ibm15/1239442-derbyall_diff.txt
> I think it is likely the index statistics update kicking in during the test. I am thinking should not be disabled for the derbyall store tests as having it kick in can cause upredictable reporting of locks pages used, etc.
> *** Start: readlocks jdk1.5.0 storeall:storemore 2012-02-01 21:11:01 ***
> 11113a11114
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> 11122a11124
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> 11131a11134
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> 11138a11142
> > APP |UserTran|ROW |1 |S |A |(2,6) |GRANT|ACTIVE
> Test Failed.
> *** End: readlocks jdk1.5.0 storeall:storemore 2012-02-01 21:13:31 ***
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira