Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cosbench runs into ArrayIndexOutOfBoundsException on both 0.4.2.c3 and 0.4.2.c4 #323

Open
atheism opened this issue Jul 4, 2016 · 0 comments · Fixed by open-io/cosbench#10

Comments

@atheism
Copy link

atheism commented Jul 4, 2016

When ran ceph s3 tests against our own server. we got the following error in system.log.
2016-07-04 09:51:32,568 [ERROR] [AbstractAgent] - unexpected exception
java.lang.ArrayIndexOutOfBoundsException: 0
at com.intel.cosbench.driver.operator.AbstractOperator.errorStatisticsHandle(AbstractOperator.java:117)
at com.intel.cosbench.driver.operator.Reader.doRead(Reader.java:103)
at com.intel.cosbench.driver.operator.Reader.operate(Reader.java:69)
at com.intel.cosbench.driver.operator.AbstractOperator.operate(AbstractOperator.java:76)
at com.intel.cosbench.driver.agent.WorkAgent.performOperation(WorkAgent.java:197)
at com.intel.cosbench.driver.agent.WorkAgent.doWork(WorkAgent.java:177)
at com.intel.cosbench.driver.agent.WorkAgent.execute(WorkAgent.java:134)
at com.intel.cosbench.driver.agent.AbstractAgent.call(AbstractAgent.java:44)
at com.intel.cosbench.driver.agent.AbstractAgent.call(AbstractAgent.java:1)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
2016-07-04 09:51:32,573 [ERROR] [AbstractAgent] - unexpected exception
java.lang.ArrayIndexOutOfBoundsException: 0
at com.intel.cosbench.driver.operator.AbstractOperator.errorStatisticsHandle(AbstractOperator.java:117)
at com.intel.cosbench.driver.operator.Reader.doRead(Reader.java:103)
at com.intel.cosbench.driver.operator.Reader.operate(Reader.java:69)
at com.intel.cosbench.driver.operator.AbstractOperator.operate(AbstractOperator.java:76)
at com.intel.cosbench.driver.agent.WorkAgent.performOperation(WorkAgent.java:197)
at com.intel.cosbench.driver.agent.WorkAgent.doWork(WorkAgent.java:177)
at com.intel.cosbench.driver.agent.WorkAgent.execute(WorkAgent.java:134)
at com.intel.cosbench.driver.agent.AbstractAgent.call(AbstractAgent.java:44)
at com.intel.cosbench.driver.agent.AbstractAgent.call(AbstractAgent.java:1)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

We have written 5000 objects in each bucket. and when we test 100 percent random read to a bucket, the problem occurs and the test is terminated.
The config file used in this test:

<storage type="s3" config="accesskey=ACCESSKEY;secretkey=SECRETKEY;proxyhost=;proxyport=;endpoint=http://192.168.1.182" />
<workstage name="main">
  <work name="main" workers="32" runtime="100">
    <operation type="read" ratio="100" config="cprefix=s3testclone1;containers=u(1,1);objects=u(1,5000)" />
  </work>
</workstage>
fvennetier added a commit to fvennetier/cosbench that referenced this issue Dec 31, 2019
Recent JVMs run with OmitStackTraceInFastThrow enabled by default. When
an exception occurs several times, the stack trace is no more generated,
but COSBench still tries to parse it, and fails miserably. One solution
is to run COSBench with -XX:-OmitStackTraceInFastThrow. For extra
security we will also ignore such empty stack traces.

Fixes: intel-cloud#323
Fixes: intel-cloud#331
fvennetier added a commit to open-io/cosbench that referenced this issue Jan 3, 2020
Recent JVMs run with OmitStackTraceInFastThrow enabled by default. When
an exception occurs several times, the stack trace is no more generated,
but COSBench still tries to parse it, and fails miserably. One solution
is to run COSBench with -XX:-OmitStackTraceInFastThrow. For extra
security we will also ignore such empty stack traces.

Fixes: intel-cloud#323
Fixes: intel-cloud#331
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant