[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[[["\u003cp\u003eThis documentation specifically addresses Cassandra heap issues within Apigee hybrid environments, and is not applicable to Apigee Edge.\u003c/p\u003e\n"],["\u003cp\u003eCassandra heap problems, indicated by \u003ccode\u003eOutOfMemoryError\u003c/code\u003e or GC warnings in pod logs, can lead to slowness or \u003ccode\u003eDatastore\u003c/code\u003e errors in Apigee hybrid proxy execution.\u003c/p\u003e\n"],["\u003cp\u003eInsufficient \u003ccode\u003emaxHeapSize\u003c/code\u003e in the \u003ccode\u003eoverrides.yaml\u003c/code\u003e file is the primary cause of these heap issues, potentially due to missing or inadequate production settings.\u003c/p\u003e\n"],["\u003cp\u003eResolving this involves adjusting the \u003ccode\u003emaxHeapSize\u003c/code\u003e and \u003ccode\u003ememory\u003c/code\u003e settings in \u003ccode\u003eoverrides.yaml\u003c/code\u003e, and applying the updated configuration, and if the issue persists, scaling horizontally may be required.\u003c/p\u003e\n"],["\u003cp\u003eIf issues remain, collect diagnostic data from Cassandra pods using provided commands and share it with Google Cloud Customer Care for assistance.\u003c/p\u003e\n"]]],[],null,["# Cassandra Java heap space issues\n\n*You're viewing **Apigee** and **Apigee hybrid** documentation.\nThere is no equivalent\n[Apigee Edge](https://docs.apigee.com/api-platform/get-started/get-started) documentation for this topic.*\n| **Note:** This document is applicable for Apigee hybrid users only.\n\nSymptom\n-------\n\n\nCassandra heap issues may cause slowness in the Apigee hybrid proxy\nexecution or even `Datastore` errors. Sometimes logs are an early\nindicator, even before the onset of symptoms.\n\nError Message\n-------------\n\n\nIn Cassandra pod logs\n([Cloud Logging](/logging)), log entries\nmight be observed that are similar to the following: \n\n```java\nWARN [Service Thread] 2023-01-01 01:14:51,121 GCInspector.java:283 - G1 Young Generation GC in 2510ms...\n...\nWARN [Service Thread] 2023-01-01 01:14:51,121 GCInspector.java:283 - G1 Old Generation GC in 3100ms...\n``` \n\n```java\n2023-01-01 01:14:51,123 FailureDetector.java:278 - Not marking nodes down due to local pause of 45261214670 \u003e 5000000000\n``` \n\n```java\njava.lang.OutOfMemoryError: Java heap space\n```\n\nCause: Insufficient Java heap size\n----------------------------------\n\n### Diagnosis\n\n\nIn the `overrides.yaml` file for the Apigee hybrid\ninstallation, `maxHeapSize` is not set to a sufficient value.\nThis could be due to\n[production settings](/apigee/docs/hybrid/latest/cassandra-production#configure-cassandra-storage-settings) not applied, or current throughputs requiring a\nsetting higher than usual.\n\n### Resolution\n\n\nTo resolve the issue, adjust `maxHeapSize` and `memory`\n[accordingly](/apigee/docs/hybrid/latest/cassandra-production#configure-cassandra-storage-settings), and [apply the changes](/apigee/docs/hybrid/latest/customize-services): \n\n```java\n resources:\n requests:\n cpu: 7\n memory: 15Gi\n maxHeapSize: 8192M\n heapNewSize: 1200M\n```\n\n\nIf the issue persists with the default production configuration, try to\nincrease the values further. Note that you need to ensure that node capacity,\n[disk throughput](/apigee/docs/hybrid/latest/cassandra-production#use-ssd-storage-for-production-deployments) and\n[network bandwidth](/apigee/docs/hybrid/latest/cluster-overview#cassandra-network-requirements) are sufficient as well. \n\n```java\n resources:\n requests:\n cpu: 7\n memory: 30Gi\n maxHeapSize: 16384M\n heapNewSize: 2400M\n```\n\n\nIf the 16 GB heap setting is still not sufficient for the traffic volume, continue\nwith [horizontal scaling](/apigee/docs/hybrid/latest/cassandra-scaling#scaling-cassandra-horizontally).\n\nMust gather diagnostic information\n----------------------------------\n\n\nIf the problem persists even after following the above instructions, gather the\nfollowing diagnostic information and then contact\n[Google Cloud Customer Care](/support-hub):\n\n\nApart from the usual data you might be asked to provide, collect the\ndiagnostic data from all the Cassandra pods with the command below: \n\n```java\nfor p in $(kubectl -n apigee get pods -l app=apigee-cassandra --no-headers -o custom-columns=\":metadata.name\") ; do \\\nfor com in info describecluster failuredetector version status ring info gossipinfo compactionstats tpstats netstats cfstats proxyhistograms gcstats ; do kubectl \\\n-n apigee exec ${p} -- bash -c 'nodetool -u $APIGEE_JMX_USER -pw $APIGEE_JMX_PASSWORD '\"$com\"' 2\u003e&1 '\\\n| tee /tmp/k_cassandra_nodetool_${com}_${p}_$(date +%Y.%m.%d_%H.%M.%S).txt | head -n 40 ; echo '...' ; done; done\n```\n\n\nCompress it, and provide it in the Support case: \n\n```java\ntar -cvzf /tmp/cassandra_data_$(date +%Y.%m.%d_%H.%M.%S).tar.gz /tmp/k_cassandra_nodetool*\n```"]]
