Hi Harsh,
I need a little help. I made change to the cluster.xml file to make changes
like this. I actually copied and added the following lines of code to
address this issue.
<appender name="MY_APP"
class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>${storm.home}/logs/cexp.rtsale.log</file>
<rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"
>
<fileNamePattern>${storm.home}/logs/myapp.log.%i</fileNamePattern>
<minIndex>1</minIndex>
<maxIndex>9</maxIndex>
</rollingPolicy>
<triggeringPolicy
class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">
<maxFileSize>10MB</maxFileSize>
</triggeringPolicy>
<encoder>
<pattern>%d %-8r %m%n</pattern>
</encoder>
</appender>
<logger name="MY_PACKAGE_STRUCTURE" additivity="false">
<level value="INFO" />
<appender-ref ref="MY_APP" />
</logger>
I restarted storm after making these changes. But I dont see log file being
created and logs been written. Can you help find the issue? Thanks.
--
Kushan Maskey
817.403.7500
M. Miller & Associates <http://mmillerassociates.com/>
[email protected]
On Sat, Dec 6, 2014 at 2:03 AM, John Reilly <[email protected]> wrote:
>
> I meant that it is not in 0.9.3 release. It looks like it was merged to
> master from the security branch but is not part of a release yet.
>
>
> On Fri Dec 05 2014 at 8:22:48 PM Harsha <[email protected]> wrote:
>
>>
>> Yep my bad its in 0.9.3 and not in 0.9.2. In 0.9.2 workers uses
>> cluster.xml so you can add your log4j changes there.. In 0.9.2 workers
>> uses cluster.xml so you can add your log4j changes there.
>>
>> On Fri, Dec 5, 2014, at 04:39 PM, John Reilly wrote:
>>
>> Hi Harsha,
>> It looks like worker.xml was introduced after the 0.9.3 release.
>> Cheers,
>> John
>>
>> On Fri Dec 05 2014 at 8:38:55 AM Harsha <[email protected]> wrote:
>>
>>
>>
>> my bad its in 0.9.3 and not in 0.9.2. In 0.9.2 workers uses cluster.xml
>> so you can add your log4j changes there.
>>
>> On Fri, Dec 5, 2014, at 07:55 AM, Kushan Maskey wrote:
>>
>> Harsh,
>>
>> I could not find worker.xml in my storm package. Does it come with storm
>> 0.9.2 package? Thanks.
>>
>> --
>> Kushan Maskey
>> 817.403.7500
>> M. Miller & Associates <http://mmillerassociates.com/>
>> [email protected]
>>
>> On Thu, Dec 4, 2014 at 12:11 PM, Kushan Maskey <kushan.maskey@
>> mmillerassociates.com> wrote:
>>
>> I have not and I think I will try that. I will keep you posted.
>>
>> Thanks.
>>
>>
>> --
>> Kushan Maskey
>> 817.403.7500
>>
>> M. Miller & Associates <http://mmillerassociates.com/>
>> [email protected]
>>
>>
>> On Thu, Dec 4, 2014 at 11:30 AM, Harsha <[email protected]> wrote:
>>
>>
>>
>> Kushan,
>> Did you try modifying logback/worker.xml . Since you have
>> multiple topologies if they have distinct java packages you can add per
>> package log4j config to worker.xml . You probably might see duplicate
>> logging in worker-port.log files additional to the topology log files.
>> Thats one way I would try separating out topology logging .
>>
>> -Harsha
>>
>>
>> On Thu, Dec 4, 2014, at 09:23 AM, Parth Brahmbhatt wrote:
>>
>> Harsha is right, if you are trying to do this as part of topology
>> submission, even though the param will get accepted it will have no effect.
>> On Dec 4, 2014, at 9:01 AM, Parth Brahmbhatt <[email protected]>
>> wrote:
>>
>>
>> As the error suggests it needs to be an utterable, you can add it by
>> using the following line, the second arg must be a collection.
>> *config.put(Config.SUPERVISOR_SLOTS_PORTS, Lists.newArrayList(7000));*
>>
>> On Dec 4, 2014, at 8:58 AM, Kushan Maskey <kushan.maskey@
>> mmillerassociates.com> wrote:
>>
>>
>> Is there a way I can set supervisor_slots_port in the config in the
>> topology class? I tried to set it up like below
>>
>> *config.put(Config.SUPERVISOR_SLOTS_PORTS, 7000);*
>>
>> but I get error as below.
>>
>> *InvalidTopologyException(msg:Field supervisor.slots.ports must be an
>> Iterable of java.lang.Number*
>> Thanks.
>>
>> --
>> Kushan Maskey
>> 817.403.7500
>> M. Miller & Associates <http://mmillerassociates.com/>
>> [email protected]
>>
>>
>>
>>
>>
>> CONFIDENTIALITY NOTICE
>> NOTICE: This message is intended for the use of the individual or entity
>> to which it is addressed and may contain information that is confidential,
>> privileged and exempt from disclosure under applicable law. If the reader
>> of this message is not the intended recipient, you are hereby notified that
>> any printing, copying, dissemination, distribution, disclosure or
>> forwarding of this communication is strictly prohibited. If you have
>> received this communication in error, please contact the sender immediately
>> and delete it from your system. Thank You.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
