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

Executing test com.linkedin.dynamometer.TestDynamometerInfra stuck #100

Open
pingsutw opened this issue Jul 25, 2019 · 3 comments
Open

Executing test com.linkedin.dynamometer.TestDynamometerInfra stuck #100

pingsutw opened this issue Jul 25, 2019 · 3 comments

Comments

@pingsutw
Copy link

I try to build latest dynamometer
When it run TestDynamometerInfra, it seems it stuck at this point
Dose anything need to be pre-installed for the build

kevin@kevin-pc:~/git/dynamometer(master)$ ./gradlew build
Parallel execution is an incubating feature.

Configure project :
Building version '0.1.7' (value loaded from 'version.properties' file).

Task :dynamometer-workload:compileJava
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

Task :dynamometer-blockgen:javadoc
/home/kevin/git/dynamometer/dynamometer-blockgen/src/main/java/com/linkedin/dynamometer/blockgenerator/XMLParserMapper.java:26: warning - Tag @link: reference not found: org.apache.hadoop.hdfs.tools.offlineImageViewer.OfflineImageViewer
1 warning

Task :dynamometer-workload:javadoc
/home/kevin/git/dynamometer/dynamometer-workload/src/main/java/com/linkedin/dynamometer/workloadgenerator/TimedInputFormat.java:29: warning - WorkloadDriver#START_TIMESTAMP_MS (referenced by @value tag) is an unknown reference.
1 warning
<============-> 94% EXECUTING [6m 27s]
IDLE
IDLE
:dynamometer-infra:test > 2 tests completed
:dynamometer-infra:test > Executing test com.linkedin.dynamometer.TestDynamometerInfra
IDLE
IDLE

@xkrogen
Copy link
Collaborator

xkrogen commented Jul 31, 2019

Hi @pingsutw , besides some standard Unix utilities like tar, nothing needs to be preinstalled. Can you try running ./gradlew build --info to get more debug output?

Please note that the test can take some time (5+ minutes) because it takes some steps like downloading a Hadoop tarball, unzipping it, localizing that tarball as a resource to DataNodes it instantiates, then starting up an HDFS cluster.

@jojochuang
Copy link

I had a similar issue when i ran it on a very full host. Turns out YARN doesn't launch a job if a node is beyond 99% full. So try it on a different machine.

@pingsutw
Copy link
Author

pingsutw commented Jul 31, 2019

@xkrogen @jojochuang Thank you for your replying

Please note that the test can take some time (5+ minutes) because it takes some steps like downloading a Hadoop tarball, unzipping it, localizing that tarball as a resource to DataNodes it instantiates, then starting up an HDFS cluster.

It's weird that sometimes the test ran more than hour, and didn't finish yet
sometimes it works

I had a similar issue when i ran it on a very full host. Turns out YARN doesn't launch a job if a node is beyond 99% full. So try it on a different machine.

I have tried on different machine before, it works for me
but I just want to find this bug, and fix it

@pingsutw pingsutw reopened this Jul 31, 2019
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

No branches or pull requests

3 participants