|Deletions are marked like this.||Additions are marked like this.|
|Line 37:||Line 37:|
|For more information about configuring queue managers, See [[GettingStarted]].
Frequently Asked Questions
1. I get ": hostname nor servname provided, or not known" error on Cygwin/Windows.
You can fix this by changing hama.zookeeper.quorum variable 'localhost' to '127.0.0.1'.
2. I get ": Incorrect header or version mismatch from 127.0.0.1:52772 got version 3 expected version 4." while starting.
Please use a release of Hadoop that is compatible with the Hama Release. Please refer to our CompatibilityTable.
3. I get ": FATAL org.apache.hama.BSPMasterRunner: java.net.UnknownHostException: Invalid hostname for server: local" while starting.
This is the case if you're in the local-mode and tried to launch Hama via the start script. In this mode, nothing has to be launched. A multithreaded running utility will start when submitting your job. Please refer to Local Mode
4. When I submit a job, I see that it fails immediately without running a task.
Please look in your BSPMaster.log in the log directory under $HAMA_HOME/logs/hama-$USER-bspmaster-$HOSTNAME.log. If you see a line equal to
2012-07-28 17:45:34,708 ERROR org.apache.hama.bsp.SimpleTaskScheduler: Scheduling of job test.jar could not be done successfully. Killing it!
the scheduler could not schedule your job, because you don't have enough resources (task slots) in your cluster available. So watch closely while submitting the job, if it says
2012-07-28 17:45:34 INFO bsp.FileInputFormat: Total # of splits: 4
and your cluster shows (for example in the web UI) only 3 slots that are free, our scheduler could not successfully schedule all the tasks. If you are familiar with Hadoop, you will be confused with this behaviour. Mainly because BSP needs the tasks to run in parallel, whereas in MapReduce the map tasks are not depending on each other (so they can be processed after each other). We are sorry for the not existing error message and will fix this in near future.
5. Is there any restriction on max message sent before sync()?
In Mem-based queue case, messages is kept in memory, therefore it depends on memory available. In Spilling queue case, there's no limits.
For more information about configuring queue managers, See GettingStarted.
Still not solved?
If you have any questions or something to say to us, please subscribe to our user mailing list and post a message.