|
Error on initialization of server mk-worker (stormconf.ser is missing)
2 名作者发布了 13 个帖子
| |
|
| Moshe Bixenshpaner |
12-8-10
|
Hi guys,
I have a simple topology that puts values on a Redis server.
When I deploy it, no client gets to connect Redis, although it works perfectly fine when I run it via LocalCluster.
I attached logs and conf for the nimbus and the supervisors.
The cluster is configured as following:
- 1GB RAM for the nimbus (192.168.1.22)
- 1GB RAM for the zookeeper1 (192.168.1.31)
- 2GB RAM for the supervisor1 (192.168.1.16; 4 workers)
- 2GB RAM for the supervisor2 (192.168.1.19; 2 workers)
All machines are virtual and have JDK 6u33 x64 installed.
nimbus, supervisor1 & supervisor2 have Storm 0.8.0, ZeroMQ 2.1.7 and the latest JZMQ installed.
zookeeper1 has Python 2.6.6 (with default configuration) and Zookeeper 3.3.6 installed.
I'm not sure this is the entire problem, but I'm getting the following exception on
someof my supervisors (in our case - supervisor2):
2012-08-10 08:21:27 worker [ERROR] Error on initialization of server mk-worker
java.io.FileNotFoundException: File '/opt/storm/local/supervisor/<wbr>stormdist/DistributedSystem-1-<wbr>1344586762/stormconf.ser' does not exist</wbr></wbr>
at org.apache.commons.io.<wbr>FileUtils.openInputStream(<wbr>FileUtils.java:137)</wbr></wbr>
at org.apache.commons.io.<wbr>FileUtils.readFileToByteArray(<wbr>FileUtils.java:1135)</wbr></wbr>
at backtype.storm.config$read_<wbr>supervisor_storm_conf.invoke(<wbr>config.clj:138)</wbr></wbr>
at backtype.storm.daemon.worker$<wbr>worker_data.invoke(worker.clj:<wbr>146)</wbr></wbr>
at backtype.storm.daemon.worker$<wbr>fn__4316$exec_fn__1206__auto__<wbr>__4317.invoke(worker.clj:331)</wbr></wbr>
at clojure.lang.AFn.<wbr>applyToHelper(AFn.java:185)</wbr>
at clojure.lang.AFn.applyTo(AFn.<wbr>java:151)</wbr>
at clojure.core$apply.invoke(c ore.clj:601)
at backtype.storm.daemon.worker$<wbr>fn__4316$mk_worker__4372.<wbr>doInvoke(worker.clj:322)</wbr></wbr>
at clojure.lang.RestFn.invoke(<wbr>RestFn.java:512)</wbr>
at backtype.storm.daemon.worker$_<wbr>main.invoke(worker.clj:432)</wbr>
at clojure.lang.AFn.<wbr>applyToHelper(AFn.java:172)</wbr>
at clojure.lang.AFn.applyTo(AFn.<wbr>java:151)</wbr>
at backtype.storm.daemon.worker.<wbr>main(Unknown Source)</wbr>
2012-08-10 08:21:27 util [INFO] Halting process: ("Error on initialization")
The topology I'm trying to run requires 4 workers altogether.
So even if supervisor2 dysfunctions, the other supervisor should be able to run the entire topology on its own.
Am I doing something wrong here?
So even if supervisor2 dysfunctions, the other supervisor should be able to run the entire topology on its own.
Am I doing something wrong here?
Thanks,
Moshe.
Moshe.
|
| nathanmarz |
12-8-13
|
Are your supervisors sharing a directory over a network mount, by any chance? What happens if you turn off supervisor2 completely? Do topologies launch successfully on the other supervisor?
|
| Moshe Bixenshpaner |
12-8-14
|
No, supervisors don't share directories.
They are virtual machines created by kvm though (I'm not sure if it has anything to do with the problem).
If I have enough workers on a single supervisor, everything works perfectly fine.
It seems the coordination between the supervisors is the cause of the problem.
It seems the coordination between the supervisors is the cause of the problem.
Thanks,
Moshe.
- 显示引用文字 -
|
| nathanmarz |
12-8-14
|
The error you're facing indicates that the supervisor failed to download the configuration file from Nimbus. Can you show me the results of doing an ls -R on the supervisor local dir for the node that's getting that error? (do it while the topology is active and causing the error – that is, don't shut it down and then do the ls -R).
- 显示引用文字 -
此帖已被删除。
|
| Moshe Bixenshpaner |
12-8-14
|
Hi,
I attached the local directory and log files for nimbus and each of the supervisors.
sv2 is the supervisor that fails to load.
Thanks,
Moshe.
- 显示引用文字 -
|
| nathanmarz |
12-8-15
|
I would need you to do the ls -R while the error is happening and the topology is still active.
- 显示引用文字 -
|
| Moshe Bixenshpaner |
12-8-15
|
This is exactly what I did (only I attached a tar file or the entire local directory, instead of just attaching the output from an ls -R).
- 显示引用文字 -
|
| nathanmarz |
12-8-17
|
I don't quite understand – you said you did the ls -R a few days after the exception happened.
- 显示引用文字 -
|
| Moshe Bixenshpaner |
12-8-17
|
I deleted that post, the one I posted eventually was after I reset everything, reproduced the whole thing and attached logs and contents of local directories.
- 显示引用文字 -
|
| Moshe Bixenshpaner |
12-8-26
|
Hi Nathan,
Log files of both SV2 workers show the logs show
java.io.<wbr>FileNotFoundException: File '/opt/storm/local/supervisor/<wbr>stormdist/DistributedSystem-1-<wbr>1344956702/stormconf.ser' does not exist</wbr></wbr></wbr>followed by
Halting process: ("Error on initialization").
On another note, the ZK1 log shows that clients are disconnecting every few seconds.
- 显示引用文字 -
|
| Moshe Bixenshpaner |
12-8-26
|
Problem is solved.
There were actually two of them:
1. The documentation specify to use a specific version of ZeroMQ, JZMQ, Python and JDK but doesn't specify anything about the Zookeeper, I assumed I can use the newest version (3.3.6) but it turned out to be a bad move. After a week with poor performance,I checked the jars attached to Storm 0.8.0 and I saw that it is aimed for Zookeeper 3.3.3.
2. I'm not sure how it is with real clusters, but on virtual cluster you need to have each node specified in the /etc/hosts file of all other nodes - pay attention to the following form:
ip_address host_name.defaultdomain
Notice the .defaultdomain at the end of each host name - this was what actually solved the problem of having a cluster of supervisors working together simultaneously.
- 显示引用文字 -
扫一扫
7406
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
