Peerplays_Blockchain/peerplays_migrated

Fork 0

peerplays blockchain logs not getting pushed to elasticsearch #45

New issue

Closed

opened 2021-02-19 17:11:03 +00:00 by prandnum · 9 comments

prandnum commented

2021-02-19 17:11:03 +00:00

(Migrated from gitlab.com)

peerplays blockchain logs not getting pushed to elasticsearch

getting the following error

2031498ms th_a       db_notify.cpp:680             notify_changed_objec ] 3100000 plugin_exception: plugin exception
Error creating object from ES database, we are going to keep trying.
    {}
    th_a  es_objects.cpp:705 operator()
2031498ms th_a       db_notify.cpp:680             notify_changed_objec ] 0: 0
2032774ms th_a       db_notify.cpp:644             notify_changed_objec ] Caught plugin exception: 3100000 plugin_exception: plugin exception
Error creating object from ES database, we are going to keep trying.
    {}
    th_a  es_objects.cpp:705 operator()
2032774ms th_a       db_notify.cpp:680             notify_changed_objec ] 3100000 plugin_exception: plugin exception
Error creating object from ES database, we are going to keep trying.
    {}
    th_a  es_objects.cpp:705 operator()

Note: Steps followed are the same mentioned in the wiki

https://peerplays.atlassian.net/wiki/spaces/PROJECTS/pages/1367113733/Quick+setup+of+Elasticsearch+plugin+on+local+computer

Note: Had a discussion with Srdjan and he mentioned trying it with local testnet to narrow down the issue.

peerplays blockchain logs not getting pushed to elasticsearch getting the following error ``` 2031498ms th_a db_notify.cpp:680 notify_changed_objec ] 3100000 plugin_exception: plugin exception Error creating object from ES database, we are going to keep trying. {} th_a es_objects.cpp:705 operator() 2031498ms th_a db_notify.cpp:680 notify_changed_objec ] 0: 0 2032774ms th_a db_notify.cpp:644 notify_changed_objec ] Caught plugin exception: 3100000 plugin_exception: plugin exception Error creating object from ES database, we are going to keep trying. {} th_a es_objects.cpp:705 operator() 2032774ms th_a db_notify.cpp:680 notify_changed_objec ] 3100000 plugin_exception: plugin exception Error creating object from ES database, we are going to keep trying. {} th_a es_objects.cpp:705 operator() ``` Note: Steps followed are the same mentioned in the wiki https://peerplays.atlassian.net/wiki/spaces/PROJECTS/pages/1367113733/Quick+setup+of+Elasticsearch+plugin+on+local+computer Note: Had a discussion with Srdjan and he mentioned trying it with local testnet to narrow down the issue.

prandnum commented

2021-02-21 11:41:38 +00:00

(Migrated from gitlab.com)

changed the description

prandnum commented

2021-02-21 11:42:50 +00:00

(Migrated from gitlab.com)

changed the description

prandnum commented

2021-02-21 11:43:14 +00:00

(Migrated from gitlab.com)

@bobinson, please take a look

prandnum commented

2021-02-21 17:45:26 +00:00

(Migrated from gitlab.com)

seeing the same issue when https://github.com/peerplays-network/peerplays-utils/blob/master/son-qa-environment/init-network.sh is run on private testnet

config and logs attached

private-testnet.zip

seeing the same issue when https://github.com/peerplays-network/peerplays-utils/blob/master/son-qa-environment/init-network.sh is run on private testnet config and logs attached [private-testnet.zip](/uploads/34519f2fdb223a07268c433972cbf475/private-testnet.zip)

prandnum commented

2021-02-22 16:34:01 +00:00

(Migrated from gitlab.com)

Tried the following:

Set JVM size in elasticsearch to 12g
increased the bulk replay from 10 (as mentioned in the document) to 100(bitshares recommended default)

But the issue is still seen.

Also ES has the "http.max_content_length" parameter default is already 100mb (Maximum size of an HTTP request body)
Refer: https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-http.html

So either we have a software bug or the ini-network.sh is having some issues

@bobinson @serkixenos - we need to debug this further. Also, I think my expectation of plugin pushing blockchain logs into es might not be correct(elasticsearch-index-prefix index), please confirm.

Tried the following: 1. Set JVM size in elasticsearch to 12g 2. increased the bulk replay from 10 (as mentioned in the document) to 100(bitshares recommended default) But the issue is still seen. Also ES has the "http.max_content_length" parameter default is already 100mb (Maximum size of an HTTP request body) Refer: https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-http.html So either we have a software bug or the ini-network.sh is having some issues @bobinson @serkixenos - we need to debug this further. Also, I think my expectation of plugin pushing blockchain logs into es might not be correct(elasticsearch-index-prefix index), please confirm.

prandnum commented

2021-02-22 16:50:47 +00:00

(Migrated from gitlab.com)

mentioned in issue #46

serkixenos commented

2021-10-25 19:17:57 +00:00

(Migrated from gitlab.com)

@prandnum So, I guess this one is resolved now, because you were attaching elastic search logs to some new tickets, like here

https://gitlab.com/PBSA/peerplays/-/issues/202

@prandnum So, I guess this one is resolved now, because you were attaching elastic search logs to some new tickets, like here https://gitlab.com/PBSA/peerplays/-/issues/202

prandnum commented

2021-10-25 20:21:11 +00:00

(Migrated from gitlab.com)

assigned to @prandnum

prandnum commented

2021-10-26 19:00:16 +00:00

(Migrated from gitlab.com)

verified https://peerplays.atlassian.net/wiki/spaces/PROJECTS/pages/1367113733/Quick+setup+of+Elasticsearch+plugin+on+local+computer

verified https://peerplays.atlassian.net/wiki/spaces/PROJECTS/pages/1367113733/Quick+setup+of+Elasticsearch+plugin+on+local+computer ![elk](/uploads/946ca8d4e10a5871c263fb6e638c9d89/elk.jpg)

prandnum (Migrated from gitlab.com) closed this issue

2021-10-26 19:00:16 +00:00