problem with running tests with large number of rows #3

maysamyabandeh · 2012-03-27T09:40:50Z

at tso/ClientHandler.java which is to test the status oracle, here is the way we generate the row ids:

byte writtenSize = readOnly ? 0 : (byte) rnd.nextInt(MAX_ROW);

if MAX_ROW is larger than max unsigned byte (i.e., 127). then the result could be negative. This is because the byte sign is the 8th bit.

This closes #3

ghost assigned dgomezferro Mar 27, 2012

dgomezferro mentioned this issue May 4, 2012

Use int for rows size #10

Merged

dgomezferro closed this as completed in 533a6b3 May 4, 2012

francisco-perez-sorrosal pushed a commit that referenced this issue May 27, 2015

Catch NPE during scan (fix for issue #3) + throttle fast scanners

2bbe1f4

francisco-perez-sorrosal pushed a commit that referenced this issue Aug 15, 2016

[OMID-50]: Provide an option to reduce tso-server CPU usage

4266f29

This closes #3

gyehuda unassigned dgomezferro Jul 15, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

problem with running tests with large number of rows #3

problem with running tests with large number of rows #3

maysamyabandeh commented Mar 27, 2012

problem with running tests with large number of rows #3

problem with running tests with large number of rows #3

Comments

maysamyabandeh commented Mar 27, 2012