Hi Qi, >> I want to know is this normal and how to avoid such log.
>From Samza's perspective, I would treat these messages as red-herrings as long as your containers are up and running. The INFO messages in the ResourceManager log correspond to resources requested by your application. On a related note, I see that you are currently running Samza 0.12. I would recommend upgrading to the 0.14.1 release, since it includes multiple critical fixes <https://issues.apache.org/jira/browse/SAMZA-1484> to run stateful jobs on YARN. Best, Jagadish On Wed, Dec 26, 2018 at 6:00 PM QiShu <sh...@eefung.com> wrote: > Hi Guys, > > Now I use Samza 0.12.0 with HDP-3.0.0.0(Hadoop3.1.0). > > And everything is fine, except the ResourceManager and NodeManager > log some infomations repeatedly and very quickly, like belows: > > ===ResourceManager log=== > 2018-12-27 09:51:05,433 INFO capacity.CapacityScheduler > (CapacityScheduler.java:allocate(1200)) - Allocation for application > appattempt_1545793580017_0011_000001 : Allocation{containers=[], > strictContainers=null, fungibleContainers=[], > fungibleResources=[{AllocationRequestId: -1, Priority: -1, Capability: > <memory:1024, vCores:1>, # Containers: 0, Location: *, Relax Locality: > true, Execution Type Request: {Execution Type: GUARANTEED, Enforce > Execution Type: false}, Node Label Expression: null}], nmTokens=[], > increasedContainers=[], decreasedContainers=[], promotedContainers=[], > demotedContainers=[], previousAttemptContainers=null, > resourceLimit=<memory:307200, vCores:400>} with cluster resource : > <memory:552960, vCores:468> > 2018-12-27 09:51:05,448 INFO capacity.CapacityScheduler > (CapacityScheduler.java:allocate(1200)) - Allocation for application > appattempt_1545793580017_0018_000001 : Allocation{containers=[], > strictContainers=null, fungibleContainers=[], > fungibleResources=[{AllocationRequestId: -1, Priority: -1, Capability: > <memory:1024, vCores:1>, # Containers: 0, Location: *, Relax Locality: > true, Execution Type Request: {Execution Type: GUARANTEED, Enforce > Execution Type: false}, Node Label Expression: null}], nmTokens=[], > increasedContainers=[], decreasedContainers=[], promotedContainers=[], > demotedContainers=[], previousAttemptContainers=null, > resourceLimit=<memory:307200, vCores:400>} with cluster resource : > <memory:552960, vCores:468> > 2018-12-27 09:51:05,606 INFO capacity.CapacityScheduler > (CapacityScheduler.java:allocate(1200)) - Allocation for application > appattempt_1545793580017_0008_000001 : Allocation{containers=[], > strictContainers=null, fungibleContainers=[], > fungibleResources=[{AllocationRequestId: -1, Priority: -1, Capability: > <memory:1024, vCores:1>, # Containers: 0, Location: *, Relax Locality: > true, Execution Type Request: {Execution Type: GUARANTEED, Enforce > Execution Type: false}, Node Label Expression: null}], nmTokens=[], > increasedContainers=[], decreasedContainers=[], promotedContainers=[], > demotedContainers=[], previousAttemptContainers=null, > resourceLimit=<memory:307200, vCores:400>} with cluster resource : > <memory:552960, vCores:468> > > ===NodeManager log=== > Dec 26, 2018 12:55:06 PM > com.sun.jersey.server.wadl.generators.AbstractWadlGeneratorGrammarGenerator > attachTypes > INFO: Couldn't find grammar element for class javax.ws.rs.core.Response > Dec 26, 2018 12:55:06 PM > com.sun.jersey.server.wadl.generators.AbstractWadlGeneratorGrammarGenerator > attachTypes > INFO: Couldn't find grammar element for class javax.ws.rs.core.Response > Dec 26, 2018 12:55:06 PM > com.sun.jersey.server.wadl.generators.AbstractWadlGeneratorGrammarGenerator > attachTypes > INFO: Couldn't find grammar element for class javax.ws.rs.core.Response > Dec 26, 2018 12:55:06 PM > com.sun.jersey.server.wadl.generators.AbstractWadlGeneratorGrammarGenerator > attachTypes > INFO: Couldn't find grammar element for class javax.ws.rs.core.Response > Dec 26, 2018 12:55:06 PM > com.sun.jersey.server.wadl.generators.AbstractWadlGeneratorGrammarGenerator > attachTypes > > > I want to know is this normal and how to avoid such log. > > Thanks! > > > ———————— > Qi Shu > > -- Jagadish V, Graduate Student, Department of Computer Science, Stanford University