Hello, I am facing with a really strange issue about the "scheduler.display.resource" option. I have a storm secure cluster with only one machine node. I was using one nimbus and one supervisor. I ran the same WordCountTopology example in the following experiments and I checked the "Assigned memory (MB)" on storm UI. The results are as follows: scheduler | scheduler.display.resource | Assigned Memory default | true | 0 default | false | 164 RAS | true | 896 RAS | false | 328 *RAS=ResourceAwareScheduler
I clean up all the logs, storm-local, zookeeper and restart all daemons every time I change the configuration. Did I do something wrong? Have you seen this problem before? Is the "scheduler.display.resource" supposed to influence the assigned memory? Thanks very much! Best, Ethan Li Tech Yahoo, Software Dev Eng, Interm1908 S. First St. Champaign, IL 61820etha...@yahoo-inc.com Mobile: 812-361-1879
