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

Specifying a bad port for TACHYON_MASTER_ADDRESS can cause an OutOfMemoryError #131

Closed
nicklan opened this issue Feb 22, 2014 · 1 comment

Comments

@nicklan
Copy link
Contributor

nicklan commented Feb 22, 2014

If I specify my TACHYON_MASTER_ADDRESS with port 19999 instead of 19998 then I get the following after a few seconds:

Exception in thread "main" java.lang.OutOfMemoryError: unable to create new native thread
    at java.lang.Thread.start0(Native Method)
    at java.lang.Thread.start(Thread.java:679)
    at tachyon.master.MasterClient.connect(MasterClient.java:163)
    at tachyon.master.MasterClient.worker_register(MasterClient.java:780)
    at tachyon.worker.WorkerStorage.<init>(WorkerStorage.java:298)
    at tachyon.worker.Worker.<init>(Worker.java:65)
    at tachyon.worker.Worker.createWorker(Worker.java:167)
    at tachyon.worker.Worker.main(Worker.java:218)

My setup is a bit odd, so I'm not sure how reproducible this is, but it seems bad regardless.

@haoyuan
Copy link
Contributor

haoyuan commented Feb 22, 2014

Agree. 19999 is the webui port. We need to find a solution to the master service port safe.

@haoyuan haoyuan closed this as completed Aug 6, 2014
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

2 participants