欧美bbbwbbbw肥妇,免费乱码人妻系列日韩,一级黄片

解析Arthas協(xié)助排查線上skywalking不可用問(wèn)題

 更新時(shí)間:2022年02月28日 14:44:20   作者:凱京技術(shù)團(tuán)隊(duì)  
這篇文章主要為大家介紹了解析Arthas協(xié)助排查線上skywalking不可用的問(wèn)題詳解,有需要的朋友可以借鑒參考下,希望能夠有所幫助,祝大家多多進(jìn)步,早日升職加薪

前言

首先描述下問(wèn)題的背景,博主有個(gè)習(xí)慣,每天上下班的時(shí)候看下skywalking的trace頁(yè)面的error情況。但是某天突然發(fā)現(xiàn)生產(chǎn)環(huán)境skywalking頁(yè)面沒(méi)有任何數(shù)據(jù)了,頁(yè)面也沒(méi)有顯示任何的異常,有點(diǎn)慌,我們線上雖然沒(méi)有全面鋪開(kāi)對(duì)接skywalking,但是也有十多個(gè)應(yīng)用??戳藨?yīng)用agent端日志后,其實(shí)也不用太擔(dān)心,對(duì)應(yīng)用毫無(wú)影響。大概情況就是這樣,但是問(wèn)題還是要解決,下面就開(kāi)始排查skywalking不可用的問(wèn)題。

使用到的工具arthas

Arthas是阿里巴巴開(kāi)源的一款在線診斷java應(yīng)用程序的工具,是greys工具的升級(jí)版本,深受開(kāi)發(fā)者喜愛(ài)。當(dāng)你遇到以下類(lèi)似問(wèn)題而束手無(wú)策時(shí),Arthas可以幫助你解決:

  • 這個(gè)類(lèi)從哪個(gè) jar 包加載的?為什么會(huì)報(bào)各種類(lèi)相關(guān)的 Exception?
  • 我改的代碼為什么沒(méi)有執(zhí)行到?難道是我沒(méi) commit?分支搞錯(cuò)了?
  • 遇到問(wèn)題無(wú)法在線上 debug,難道只能通過(guò)加日志再重新發(fā)布嗎?
  • 線上遇到某個(gè)用戶(hù)的數(shù)據(jù)處理有問(wèn)題,但線上同樣無(wú)法 debug,線下無(wú)法重現(xiàn)!
  • 是否有一個(gè)全局視角來(lái)查看系統(tǒng)的運(yùn)行狀況?
  • 有什么辦法可以監(jiān)控到JVM的實(shí)時(shí)運(yùn)行狀態(tài)?
  • Arthas采用命令行交互模式,同時(shí)提供豐富的 Tab 自動(dòng)補(bǔ)全功能,進(jìn)一步方便進(jìn)行問(wèn)題的定位和診斷。

先定位問(wèn)題一

查看skywalking-oap-server.log的日志,發(fā)現(xiàn)會(huì)有一條異常瘋狂的在輸出,異常詳情如下:

2019-03-01 09:12:11,578 - org.apache.skywalking.oap.server.core.register.worker.RegisterPersistentWorker -3264081149 [DataCarrier.IndicatorPersistentWorker.endpoint_inventory.Consumser.0.Thread] ERROR [] - Validation Failed: 1: id is too long, must be no longer than 512 bytes but was: 684;
org.elasticsearch.action.ActionRequestValidationException: Validation Failed: 1: id is too long, must be no longer than 512 bytes but was: 684;
        at org.elasticsearch.action.ValidateActions.addValidationError(ValidateActions.java:26) ~[elasticsearch-6.3.2.jar:6.3.2]
        at org.elasticsearch.action.index.IndexRequest.validate(IndexRequest.java:183) ~[elasticsearch-6.3.2.jar:6.3.2]
        at org.elasticsearch.client.RestHighLevelClient.performRequest(RestHighLevelClient.java:515) ~[elasticsearch-rest-high-level-client-6.3.2.jar:6.3.2]
        at org.elasticsearch.client.RestHighLevelClient.performRequestAndParseEntity(RestHighLevelClient.java:508) ~[elasticsearch-rest-high-level-client-6.3.2.jar:6.3.2]
        at org.elasticsearch.client.RestHighLevelClient.index(RestHighLevelClient.java:348) ~[elasticsearch-rest-high-level-client-6.3.2.jar:6.3.2]
        at org.apache.skywalking.oap.server.library.client.elasticsearch.ElasticSearchClient.forceInsert(ElasticSearchClient.java:141) ~[library-client-6.0.0-alpha.jar:6.0.0-alpha]
        at org.apache.skywalking.oap.server.storage.plugin.elasticsearch.base.RegisterEsDAO.forceInsert(RegisterEsDAO.java:66) ~[storage-elasticsearch-plugin-6.0.0-alpha.jar:6.0.0-alpha]
        at org.apache.skywalking.oap.server.core.register.worker.RegisterPersistentWorker.lambda$onWork$0(RegisterPersistentWorker.java:83) ~[server-core-6.0.0-alpha.jar:6.0.0-alpha]
        at java.util.HashMap$Values.forEach(HashMap.java:981) [?:1.8.0_201]
        at org.apache.skywalking.oap.server.core.register.worker.RegisterPersistentWorker.onWork(RegisterPersistentWorker.java:74) [server-core-6.0.0-alpha.jar:6.0.0-alpha]
        at org.apache.skywalking.oap.server.core.register.worker.RegisterPersistentWorker.access$100(RegisterPersistentWorker.java:35) [server-core-6.0.0-alpha.jar:6.0.0-alpha]
        at org.apache.skywalking.oap.server.core.register.worker.RegisterPersistentWorker$PersistentConsumer.consume(RegisterPersistentWorker.java:120) [server-core-6.0.0-alpha.jar:6.0.0-alpha]
        at org.apache.skywalking.apm.commons.datacarrier.consumer.ConsumerThread.consume(ConsumerThread.java:101) [apm-datacarrier-6.0.0-alpha.jar:6.0.0-alpha]
        at org.apache.skywalking.apm.commons.datacarrier.consumer.ConsumerThread.run(ConsumerThread.java:68) [apm-datacarrier-6.0.0-alpha.jar:6.0.0-alpha]
2019-03-01 09:12:11,627 - org.apache.skywalking.oap.server.core.register.worker.RegisterPersistentWorker -3264081198 [DataCarrier.IndicatorPersistentWorker.endpoint_inventory.Consumser.0.Thread] ERROR [] - Validation Failed: 1: id is too long, must be no longer than 512 bytes but was: 684;
org.elasticsearch.action.ActionRequestValidationException: Validation Failed: 1: id is too long, must be no longer than 512 bytes but was: 684;
        at org.elasticsearch.action.ValidateActions.addValidationError(ValidateActions.java:26) ~[elasticsearch-6.3.2.jar:6.3.2]
        at org.elasticsearch.action.index.IndexRequest.validate(IndexRequest.java:183) ~[elasticsearch-6.3.2.jar:6.3.2]
        at org.elasticsearch.client.RestHighLevelClient.performRequest(RestHighLevelClient.java:515) ~[elasticsearch-rest-high-level-client-6.3.2.jar:6.3.2]
        at org.elasticsearch.client.RestHighLevelClient.performRequestAndParseEntity(RestHighLevelClient.java:508) ~[elasticsearch-rest-high-level-client-6.3.2.jar:6.3.2]
        at org.elasticsearch.client.RestHighLevelClient.index(RestHighLevelClient.java:348) ~[elasticsearch-rest-high-level-client-6.3.2.jar:6.3.2]
        at org.apache.skywalking.oap.server.library.client.elasticsearch.ElasticSearchClient.forceInsert(ElasticSearchClient.java:141) ~[library-client-6.0.0-alpha.jar:6.0.0-alpha]
        at org.apache.skywalking.oap.server.storage.plugin.elasticsearch.base.RegisterEsDAO.forceInsert(RegisterEsDAO.java:66) ~[storage-elasticsearch-plugin-6.0.0-alpha.jar:6.0.0-alpha]
        at org.apache.skywalking.oap.server.core.register.worker.RegisterPersistentWorker.lambda$onWork$0(RegisterPersistentWorker.java:83) ~[server-core-6.0.0-alpha.jar:6.0.0-alpha]
        at java.util.HashMap$Values.forEach(HashMap.java:981) [?:1.8.0_201]
        at org.apache.skywalking.oap.server.core.register.worker.RegisterPersistentWorker.onWork(RegisterPersistentWorker.java:74) [server-core-6.0.0-alpha.jar:6.0.0-alpha]
        at org.apache.skywalking.oap.server.core.register.worker.RegisterPersistentWorker.access$100(RegisterPersistentWorker.java:35) [server-core-6.0.0-alpha.jar:6.0.0-alpha]
        at org.apache.skywalking.oap.server.core.register.worker.RegisterPersistentWorker$PersistentConsumer.consume(RegisterPersistentWorker.java:120) [server-core-6.0.0-alpha.jar:6.0.0-alpha]
        at org.apache.skywalking.apm.commons.datacarrier.consumer.ConsumerThread.consume(ConsumerThread.java:101) [apm-datacarrier-6.0.0-alpha.jar:6.0.0-alpha]
        at org.apache.skywalking.apm.commons.datacarrier.consumer.ConsumerThread.run(ConsumerThread.java:68) [apm-datacarrier-6.0.0-alpha.jar:6.0.0-alpha]

可以看到,上面的異常輸出的時(shí)間節(jié)點(diǎn),以這種頻率在瘋狂的刷新。通過(guò)異常message,得知到是因?yàn)閟kywalking在寫(xiě)elasticsearch時(shí),索引的id太長(zhǎng)了。下面是elasticsearch的源碼:

        if (id != null && id.getBytes(StandardCharsets.UTF_8).length > 512) {
            validationException = addValidationError("id is too long, must be no longer than 512 bytes but was: " +
                            id.getBytes(StandardCharsets.UTF_8).length, validationException);
        }

問(wèn)題一:

通過(guò)日志,初步定位是哪個(gè)系統(tǒng)的url太長(zhǎng),skywalking在注冊(cè)u(píng)rl數(shù)據(jù)時(shí)觸發(fā)elasticsearch針對(duì)索引id校驗(yàn)的異常,而skywalking注冊(cè)失敗后會(huì)不斷的重試,所以才有了上面日志不斷刷的現(xiàn)象。

問(wèn)題解決:

elasticsearch client在寫(xiě)es前通過(guò)硬編碼的方式寫(xiě)死了索引id的長(zhǎng)度不能超過(guò)512字節(jié)大小。也就是我們不能通過(guò)從ES側(cè)找解決方案了?;氐疆惓5膍essage,只能看到提示id太長(zhǎng),并沒(méi)有寫(xiě)明id具體是什么,這個(gè)異常提示其實(shí)是不合格的,博主覺(jué)得應(yīng)該把id的具體內(nèi)容拋出來(lái),問(wèn)題就簡(jiǎn)單了。因?yàn)楫惓](méi)有明確提示,系統(tǒng)又比較多,不能十多個(gè)系統(tǒng)依次關(guān)閉重啟來(lái)驗(yàn)證到底是哪個(gè)系統(tǒng)的哪個(gè)url有問(wèn)題。這個(gè)時(shí)候Arthas就派上用場(chǎng)了,在不重啟應(yīng)用不開(kāi)啟debug模式下,查看實(shí)例中的屬性對(duì)象。下面通過(guò)Arthas找到具體的url。

從異常中得知,org.elasticsearch.action.index.IndexRequest這個(gè)類(lèi)的validate方法觸發(fā)的,這個(gè)方法是沒(méi)有入?yún)⒌?,校?yàn)的id屬性其實(shí)是對(duì)象本身的屬性,那么我們使用Arthas的watch指令來(lái)看下這個(gè)實(shí)例id屬性。先介紹下watch的用法:

功能說(shuō)明

讓你能方便的觀察到指定方法的調(diào)用情況。能觀察到的范圍為:返回值、拋出異常、入?yún)?,通過(guò)編寫(xiě) OGNL 表達(dá)式進(jìn)行對(duì)應(yīng)變量的查看。

參數(shù)說(shuō)明

watch 的參數(shù)比較多,主要是因?yàn)樗茉?4 個(gè)不同的場(chǎng)景觀察對(duì)象

參數(shù)名稱(chēng)參數(shù)說(shuō)明
class-pattern類(lèi)名表達(dá)式匹配
method-pattern方法名表達(dá)式匹配
express觀察表達(dá)式
condition-express條件表達(dá)式
[b]在方法調(diào)用之前觀察
[e]在方法異常之后觀察
[s]在方法返回之后觀察
[f]在方法結(jié)束之后(正常返回和異常返回)觀察
[E]開(kāi)啟正則表達(dá)式匹配,默認(rèn)為通配符匹配
[x:]指定輸出結(jié)果的屬性遍歷深度,默認(rèn)為 1

從上面的用法說(shuō)明結(jié)合異常信息,我們得到了如下的指令腳本:

watch org.elasticsearch.action.index.IndexRequest validate "target"

執(zhí)行后,就看到了我們希望了解到的內(nèi)容,如:

索引id的具體內(nèi)容看到后,就好辦了。我們暫時(shí)把定位到的這個(gè)應(yīng)用啟動(dòng)腳本中的的skywalking agent移除后(計(jì)劃后面重新設(shè)計(jì)下接口)重啟了下系統(tǒng)驗(yàn)證下。果然瘋狂輸出的日志停住了,但是問(wèn)題并沒(méi)完全解決,skywalking頁(yè)面上的數(shù)據(jù)還是沒(méi)有恢復(fù)。

定位問(wèn)題二

skywalking數(shù)據(jù)存儲(chǔ)使用了elasticsearch,頁(yè)面沒(méi)有數(shù)據(jù),很有可能是elasticsearch出問(wèn)題了。查看elasticsearch日志后,發(fā)現(xiàn)elasticsearch正在瘋狂的GC,日志如:

: 139939K->3479K(153344K), 0.0285655 secs] 473293K->336991K(5225856K), 0.0286918 secs] [Times: user=0.05 sys=0.00, real=0.03 secs] 
2019-02-28T20:05:38.276+0800: 3216940.387: Total time for which application threads were stopped: 0.0301495 seconds, Stopping threads took: 0.0001549 seconds
2019-02-28T20:05:38.535+0800: 3216940.646: [GC (Allocation Failure) 2019-02-28T20:05:38.535+0800: 3216940.646: [ParNew
Desired survivor size 8716288 bytes, new threshold 6 (max 6)
- age   1:    1220136 bytes,    1220136 total
- age   2:     158496 bytes,    1378632 total
- age   3:      88200 bytes,    1466832 total
- age   4:      46240 bytes,    1513072 total
- age   5:     126584 bytes,    1639656 total
- age   6:     159224 bytes,    1798880 total
: 139799K->3295K(153344K), 0.0261667 secs] 473311K->336837K(5225856K), 0.0263158 secs] [Times: user=0.06 sys=0.00, real=0.03 secs] 
2019-02-28T20:05:38.562+0800: 3216940.673: Total time for which application threads were stopped: 0.0276971 seconds, Stopping threads took: 0.0001030 seconds
2019-02-28T20:05:38.901+0800: 3216941.012: [GC (Allocation Failure) 2019-02-28T20:05:38.901+0800: 3216941.012: [ParNew
Desired survivor size 8716288 bytes, new threshold 6 (max 6)

問(wèn)題二:

查詢(xún)后得知,elasticsearch的內(nèi)存配置偏大了,GC時(shí)間太長(zhǎng),導(dǎo)致elasticsearch脫離服務(wù)了。elasticsearch所在主機(jī)的內(nèi)存是8G的實(shí)際內(nèi)存7.6G,剛開(kāi)始配置了5G的堆內(nèi)存大小,可能Full GC的時(shí)候耗時(shí)太久了。查詢(xún)elasticsearch官方文檔后,得到如下的jvm優(yōu)化建議:

  • 將最小堆大?。?code>Xms)和最大堆大?。?code>Xmx)設(shè)置為彼此相等。
  • Elasticsearch可用的堆越多,它可用于緩存的內(nèi)存就越多。但請(qǐng)注意,過(guò)多的堆可能會(huì)使您陷入長(zhǎng)時(shí)間的垃圾收集暫停。
  • 設(shè)置Xmx為不超過(guò)物理RAM的50%,以確保有足夠的物理RAM用于內(nèi)核文件系統(tǒng)緩存。
  • 不要設(shè)置Xmx為JVM用于壓縮對(duì)象指針(壓縮oops)的截止值之上; 確切的截止值變化但接近32 GB。

問(wèn)題解決:

根據(jù)Xmx不超過(guò)物理RAM的50%上面的jvm優(yōu)化建議。后面將Xms和Xmx都設(shè)置成了3G。然后先停掉skywalking(由于skywalking中會(huì)緩存部分?jǐn)?shù)據(jù),如果直接先停ES,會(huì)報(bào)索引找不到的類(lèi)似異常,這個(gè)大部分skywalking用戶(hù)應(yīng)該有遇到過(guò)),清空skywalking緩存目錄下的內(nèi)容,如:

在重啟elasticsearch,接著啟動(dòng)skywalking后頁(yè)面終于恢復(fù)了

結(jié)語(yǔ)

整個(gè)問(wèn)題排查到解決大概花了半天時(shí)間,幸好一點(diǎn)也不影響線上應(yīng)用的使用,這個(gè)要得益于skywalking的設(shè)計(jì),不然就是大災(zāi)難了。然后要感謝下Arthas的技術(shù)團(tuán)隊(duì),寫(xiě)了這么好用的一款產(chǎn)品并且開(kāi)源了,如果沒(méi)有Arthas,這個(gè)問(wèn)題真的不好定位,甚至一度想到了換掉elasticsearch,采用mysql來(lái)解決索引id過(guò)長(zhǎng)的問(wèn)題。Arthas真的是線上找問(wèn)題的利器,博主在Arthas剛面世的時(shí)候就關(guān)注了,并且一直在公司推廣使用,在這里再硬推一波。

以上就是解析Arthas協(xié)助排查線上skywalking不可用問(wèn)題的詳細(xì)內(nèi)容,更多關(guān)于Arthas排查線上skywalking不可用的資料請(qǐng)關(guān)注腳本之家其它相關(guān)文章!

相關(guān)文章

最新評(píng)論