Users can pass the arguments to the JDK tools. So it exposes all the power of those tools. If we have to write the code we are doing the duplicate work. Also it doesn't evolve with the new features of the JVM, but the tools will and we just have to change the arguments that we pass.
On Mon, May 23, 2016 at 11:15 AM Vlad Rozov <[email protected]> wrote: > What is the purpose of the new process? Why that information can't be > collected directly from JVM and passed to app master using heartbeat? > > Thank you, > Vlad > > On 5/23/16 10:57, Sandesh Hegde wrote: > > Hello All, > > > > Getting various information from the StreamingConatainers is a useful > > feature to have. > > As StreamingContainers are JVMs, various JDK tools can be used to get the > > information. > > > > So the idea is to spawn the new process from the streaming containers and > > return the information via Stram. > > > > Recently we have added the feature to get stack trace I have modified > that > > to show the idea I am talking about. > > > > Here is the pull request, the purpose of that is to show the idea, let me > > know your thoughts. > > https://github.com/apache/incubator-apex-core/pull/340 > > > > I have not created a jira yet, wanted to check the viability of the idea. > > > > Thanks > > Sandesh > > > >
