Welcome!

@DevOpsSummit Authors: Yeshim Deniz, Flint Brenton, Liz McMillan, Elizabeth White, Pat Romanski

Related Topics: @DevOpsSummit, Java IoT, Microservices Expo, Microsoft Cloud, Machine Learning , @CloudExpo

@DevOpsSummit: Blog Post

DevOps Role in Troubleshooting JVM Issues | @DevOpsSummit [#DevOps]

Application developers can deploy their applications with success in a staging or QA environment

The JVM issues vary from Java OutOfMemory Error to JVM Crash. Application developers might be not completely equipped to determine the root cause of the issue, hence DevOps can play a vital role in narrowing down the issue and connecting the right people/team to rectify the problem.

Application developers can deploy their applications with success in a staging or QA environment and broadcast that the application is working fine. However, the staging or QA environment is not completely identical with production at - least with respect to load. Due to huge load, the application can behave differently. In order to prevent an occurrence of these kinds of scenarios, it is a good practice to engage a DevOps team [with right JVM skills] to proactively analyze the running application. Proactive engagement of a DevOps team will be beneficial for the organization and for the development team as well.

As a proactive engagement, the DevOps team needs to conduct an analysis on the collected memory snapshot.The memory snapshot can be gathered at regular intervals time and multiple samples of the same, so that a good picture of what is happening internally is known.

By employing appropriate JVM diagnostics tools, the DevOps team can provide recommendations to application developers with respect to memory consumption, memory reserved or memory wasted in Java collections.The topmost consumer of Java Heap memory, classes loaded, object promotion rate,object liveness, object references and many more details can be shared with application developers proactively. These in-depth details will provide application developers with insight into the application behavior and help identify any potential issues.

Apart from conducting memory-related analysis, the DevOps team can look into the performance of the application and determine the root cause of the degraded performance (if any). With regard to this, employing the right tool and conducting analysis on Garbage Collection activities will reveal whether the poor performance is due to GC or outside of the GC. The Memory Analyzer tool, which is available as a plugin to Eclipse, can be employed to conduct memory-related analysis and gather enough information. In the same pattern, the plugin " Garbage Collection Memory Visualizer" can be employed to conduct analysis on verbose GC data.

As a case study I would like to share one of the scenarios that we encountered in our organization and how we isolated the issue before engaging the right team to fix it. One of our customers upgraded to the latest application release from a previous release and noticed a significant performance degradation in the throughput. As a first step, we confirmed the customer's claim by reproducing the reported issue in our environment. Having a local reproduction environment provided us with various opportunities to try out various things when narrowing down the issue. After the first level of analysis, we confirmed the area or component that was contributing to the observed behavior and a command-line parameter was recommended to workaround the issue.The provided recommendation was tested in our local reproduction environment with success and this gave us the confidence that the  issue can be overcome with the current recommendation.

On further analysis, we engaged the appropriate tool to determine the percentage of time consumed and captured the snapshots with the latest release and the previous release where the issue was not noticed.This level of analysis revealed the exact area where more time was spent. Once these snapshots were shared with the development team, the development team's task was much easier as the area of code was already narrowed down for fixing.This way, we isolated the issue and helped the customer overcome the problem.

More Stories By ChandraShekar Dattatreya

Chandra Shekara Dattatreya is a DevOps guy working in a Fortune-500 company and has 10+ years' of experience debugging JVM-related issues. In the course of debugging, he has encountered multiple scenarios from various customers and provided solutions to all of them with success. In his current role, he is engaged in identifying and resolving JVM-related issues for an e-commerce company.

@DevOpsSummit Stories
JETRO showcased Japan Digital Transformation Pavilion at SYS-CON's 21st International Cloud Expo® at the Santa Clara Convention Center in Santa Clara, CA. The Japan External Trade Organization (JETRO) is a non-profit organization that provides business support services to companies expanding to Japan. With the support of JETRO's dedicated staff, clients can incorporate their business; receive visa, immigration, and HR support; find dedicated office space; identify local government subsidies; get tailored market studies; and more.
René Bostic is the Technical VP of the IBM Cloud Unit in North America. Enjoying her career with IBM during the modern millennial technological era, she is an expert in cloud computing, DevOps and emerging cloud technologies such as Blockchain. Her strengths and core competencies include a proven record of accomplishments in consensus building at all levels to assess, plan, and implement enterprise and cloud computing solutions. René is a member of the Society of Women Engineers (SWE) and a member of the Society of Information Management (SIM) Atlanta Chapter. She received a Business and Economics degree with a minor in Computer Science from St. Andrews Presbyterian University (Laurinburg, North Carolina). She resides in metro-Atlanta (Georgia).
In this presentation, you will learn first hand what works and what doesn't while architecting and deploying OpenStack. Some of the topics will include:- best practices for creating repeatable deployments of OpenStack- multi-site considerations- how to customize OpenStack to integrate with your existing systems and security best practices.
"With Digital Experience Monitoring what used to be a simple visit to a web page has exploded into app on phones, data from social media feeds, competitive benchmarking - these are all components that are only available because of some type of digital asset," explained Leo Vasiliou, Director of Web Performance Engineering at Catchpoint Systems, in this SYS-CON.tv interview at DevOps Summit at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
It is ironic, but perhaps not unexpected, that many organizations who want the benefits of using an Agile approach to deliver software use a waterfall approach to adopting Agile practices: they form plans, they set milestones, and they measure progress by how many teams they have engaged. Old habits die hard, but like most waterfall software projects, most waterfall-style Agile adoption efforts fail to produce the results desired. The problem is that to get the results they want, they have to change their culture and cultures are very hard to change. To paraphrase Peter Drucker, "culture eats Agile for breakfast." Successful approaches are opportunistic and leverage the power of self-organization to achieve lasting change.