Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

indexer sync stops #269

Closed
dev-dantealighieri opened this issue Jan 15, 2025 · 14 comments
Closed

indexer sync stops #269

dev-dantealighieri opened this issue Jan 15, 2025 · 14 comments
Assignees
@Kammerlo
Labels
bug Something isn't working

Comments

@dev-dantealighieri
Copy link

hi, i installed rosetta via your docker compose, after some point it stops synchronizing, when i restart it starts again.

i dont have resource issue, 128 ram, 24 cores, more than enough disk space

can you help me whats the problem? thanks

heres the outputs of cardanofoundation/cardano-rosetta-java-indexer:main

2025-01-15T07:38:52.724Z DEBUG 1 --- [ntLoopGroup-7-1] c.b.c.y.c.p.keepalive.KeepAliveAgent     : MsgKeepAliveResponse: MsgKeepAliveResponse(cookie=28512)
2025-01-15T07:39:02.722Z DEBUG 1 --- [               ] c.b.c.y.c.p.k.s.KeepAliveSerializers     : MsgKeepAlive (serialized) : 8200195026
2025-01-15T07:39:02.727Z DEBUG 1 --- [ntLoopGroup-7-1] c.b.c.y.c.p.keepalive.KeepAliveAgent     : MsgKeepAliveResponse: MsgKeepAliveResponse(cookie=20518)
2025-01-15T07:39:12.723Z DEBUG 1 --- [               ] c.b.c.y.c.p.k.s.KeepAliveSerializers     : MsgKeepAlive (serialized) : 8200193611
2025-01-15T07:39:12.725Z DEBUG 1 --- [ntLoopGroup-7-1] c.b.c.y.c.p.keepalive.KeepAliveAgent     : MsgKeepAliveResponse: MsgKeepAliveResponse(cookie=13841)
2025-01-15T07:39:17.811Z  WARN 1 --- [ntLoopGroup-5-7] i.netty.channel.DefaultChannelPipeline   : An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.

java.net.SocketException: Connection reset
	at java.base/sun.nio.ch.SocketChannelImpl.throwConnectionReset(SocketChannelImpl.java:401) ~[na:na]
	at java.base/sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:434) ~[na:na]
	at io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:255) ~[netty-buffer-4.1.107.Final.jar!/:4.1.107.Final]
	at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1132) ~[netty-buffer-4.1.107.Final.jar!/:4.1.107.Final]
	at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:357) ~[netty-transport-4.1.107.Final.jar!/:4.1.107.Final]
	at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:151) ~[netty-transport-4.1.107.Final.jar!/:4.1.107.Final]
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788) ~[netty-transport-4.1.107.Final.jar!/:4.1.107.Final]
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724) ~[netty-transport-4.1.107.Final.jar!/:4.1.107.Final]
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650) ~[netty-transport-4.1.107.Final.jar!/:4.1.107.Final]
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562) ~[netty-transport-4.1.107.Final.jar!/:4.1.107.Final]
	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) ~[netty-common-4.1.107.Final.jar!/:4.1.107.Final]
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[netty-common-4.1.107.Final.jar!/:4.1.107.Final]
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[netty-common-4.1.107.Final.jar!/:4.1.107.Final]
	at java.base/java.lang.Thread.run(Thread.java:1583) ~[na:na]

2025-01-15T07:39:17.812Z  INFO 1 --- [ntLoopGroup-5-7] c.b.c.yaci.core.network.NodeClient       : Connection closed !!!
2025-01-15T07:39:17.812Z  INFO 1 --- [ntLoopGroup-5-7] c.b.cardano.yaci.core.network.Session    : Disposing the session !!!
2025-01-15T07:39:17.812Z  WARN 1 --- [ntLoopGroup-5-7] c.b.c.yaci.core.network.NodeClient       : Trying to reconnect !!!
2025-01-15T07:39:17.814Z  INFO 1 --- [ntLoopGroup-5-8] c.b.cardano.yaci.core.network.Session    : Connection established
2025-01-15T07:39:17.814Z  INFO 1 --- [ntLoopGroup-5-8] c.b.c.yaci.core.network.NodeClient       : Connected !!!
2025-01-15T07:39:17.817Z  INFO 1 --- [ntLoopGroup-5-8] c.b.c.y.c.p.handshake.HandshakeAgent     : Handshake Ok!!! AcceptVersion(versionNumber=14, versionData=N2NVersionData(initiatorOnlyDiffusionMode=true, peerSharing=0, query=false))
2025-01-15T07:39:17.817Z DEBUG 1 --- [ntLoopGroup-5-8] c.b.c.y.c.p.k.s.KeepAliveSerializers     : MsgKeepAlive (serialized) : 82001904d2
2025-01-15T07:39:17.822Z DEBUG 1 --- [ntLoopGroup-5-8] c.b.c.y.c.p.keepalive.KeepAliveAgent     : MsgKeepAliveResponse: MsgKeepAliveResponse(cookie=1234)
2025-01-15T07:39:22.723Z DEBUG 1 --- [               ] c.b.c.y.c.p.k.s.KeepAliveSerializers     : MsgKeepAlive (serialized) : 820019e25a
2025-01-15T07:39:22.729Z DEBUG 1 --- [ntLoopGroup-7-1] c.b.c.y.c.p.keepalive.KeepAliveAgent     : MsgKeepAliveResponse: MsgKeepAliveResponse(cookie=57946)
2025-01-15T07:39:32.723Z DEBUG 1 --- [               ] c.b.c.y.c.p.k.s.KeepAliveSerializers     : MsgKeepAlive (serialized) : 8200198be5
2025-01-15T07:39:32.725Z DEBUG 1 --- [ntLoopGroup-7-1] c.b.c.y.c.p.keepalive.KeepAliveAgent     : MsgKeepAliveResponse: MsgKeepAliveResponse(cookie=35813)
2025-01-15T07:39:42.724Z DEBUG 1 --- [               ] c.b.c.y.c.p.k.s.KeepAliveSerializers     : MsgKeepAlive (serialized) : 82001997ec
2025-01-15T07:39:42.725Z DEBUG 1 --- [ntLoopGroup-7-1] c.b.c.y.c.p.keepalive.KeepAliveAgent     : MsgKeepAliveResponse: MsgKeepAliveResponse(cookie=38892)
2025-01-15T07:39:52.724Z DEBUG 1 --- [               ] c.b.c.y.c.p.k.s.KeepAliveSerializers     : MsgKeepAlive (serialized) : 8200199213
2025-01-15T07:39:52.728Z DEBUG 1 --- [ntLoopGroup-7-1] c.b.c.y.c.p.keepalive.KeepAliveAgent     : MsgKeepAliveResponse: MsgKeepAliveResponse(cookie=37395)
2025-01-15T07:40:02.725Z DEBUG 1 --- [               ] c.b.c.y.c.p.k.s.KeepAliveSerializers     : MsgKeepAlive (serialized) : 820019c954
2025-01-15T07:40:02.726Z DEBUG 1 --- [ntLoopGroup-7-1] c.b.c.y.c.p.keepalive.KeepAliveAgent     : MsgKeepAliveResponse: MsgKeepAliveResponse(cookie=51540)
2025-01-15T07:40:12.725Z DEBUG 1 --- [               ] c.b.c.y.c.p.k.s.KeepAliveSerializers     : MsgKeepAlive (serialized) : 8200198dbc
2025-01-15T07:40:12.738Z DEBUG 1 --- [ntLoopGroup-7-1] c.b.c.y.c.p.keepalive.KeepAliveAgent     : MsgKeepAliveResponse: MsgKeepAliveResponse(cookie=36284)
2025-01-15T07:40:22.725Z DEBUG 1 --- [               ] c.b.c.y.c.p.k.s.KeepAliveSerializers     : MsgKeepAlive (serialized) : 82001999a0
2025-01-15T07:40:22.726Z DEBUG 1 --- [ntLoopGroup-7-1] c.b.c.y.c.p.keepalive.KeepAliveAgent     : MsgKeepAliveResponse: MsgKeepAliveResponse(cookie=39328)
2025-01-15T07:40:32.726Z DEBUG 1 --- [               ] c.b.c.y.c.p.k.s.KeepAliveSerializers     : MsgKeepAlive (serialized) : 8200194e10
2025-01-15T07:40:32.726Z DEBUG 1 --- [ntLoopGroup-7-1] c.b.c.y.c.p.keepalive.KeepAliveAgent     : MsgKeepAliveResponse: MsgKeepAliveResponse(cookie=19984)
2025-01-15T07:40:42.726Z DEBUG 1 --- [               ] c.b.c.y.c.p.k.s.KeepAliveSerializers     : MsgKeepAlive (serialized) : 8200198bbb
2025-01-15T07:40:42.726Z DEBUG 1 --- [ntLoopGroup-7-1] c.b.c.y.c.p.keepalive.KeepAliveAgent     : MsgKeepAliveResponse: MsgKeepAliveResponse(cookie=35771)
2025-01-15T07:40:52.726Z DEBUG 1 --- [               ] c.b.c.y.c.p.k.s.KeepAliveSerializers     : MsgKeepAlive (serialized) : 8200195a1c
2025-01-15T07:40:52.729Z DEBUG 1 --- [ntLoopGroup-7-1] c.b.c.y.c.p.keepalive.KeepAliveAgent     : MsgKeepAliveResponse: MsgKeepAliveResponse(cookie=23068)
2025-01-15T07:40:54.826Z  WARN 1 --- [ntLoopGroup-5-8] i.netty.channel.DefaultChannelPipeline   : An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.

java.net.SocketException: Connection reset
	at java.base/sun.nio.ch.SocketChannelImpl.throwConnectionReset(SocketChannelImpl.java:401) ~[na:na]
	at java.base/sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:434) ~[na:na]
	at io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:255) ~[netty-buffer-4.1.107.Final.jar!/:4.1.107.Final]
	at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1132) ~[netty-buffer-4.1.107.Final.jar!/:4.1.107.Final]
	at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:357) ~[netty-transport-4.1.107.Final.jar!/:4.1.107.Final]
	at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:151) ~[netty-transport-4.1.107.Final.jar!/:4.1.107.Final]
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788) ~[netty-transport-4.1.107.Final.jar!/:4.1.107.Final]
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724) ~[netty-transport-4.1.107.Final.jar!/:4.1.107.Final]
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650) ~[netty-transport-4.1.107.Final.jar!/:4.1.107.Final]
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562) ~[netty-transport-4.1.107.Final.jar!/:4.1.107.Final]
	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) ~[netty-common-4.1.107.Final.jar!/:4.1.107.Final]
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[netty-common-4.1.107.Final.jar!/:4.1.107.Final]
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[netty-common-4.1.107.Final.jar!/:4.1.107.Final]
	at java.base/java.lang.Thread.run(Thread.java:1583) ~[na:na]

2025-01-15T07:40:54.827Z  INFO 1 --- [ntLoopGroup-5-8] c.b.c.yaci.core.network.NodeClient       : Connection closed !!!
2025-01-15T07:40:54.827Z  INFO 1 --- [ntLoopGroup-5-8] c.b.cardano.yaci.core.network.Session    : Disposing the session !!!
2025-01-15T07:40:54.827Z  WARN 1 --- [ntLoopGroup-5-8] c.b.c.yaci.core.network.NodeClient       : Trying to reconnect !!!
2025-01-15T07:40:54.828Z  INFO 1 --- [ntLoopGroup-5-9] c.b.cardano.yaci.core.network.Session    : Connection established

node outputs are looking normal

[872abc84:cardano.node.ChainDB:Notice:40] [2025-01-15 07:43:53.23 UTC] Chain extended, new tip: b5103a81fb964ccd9163d6087c593d038aa52a04127bee69aaebd505fd2d2657 at slot 1620473
[872abc84:cardano.node.ChainDB:Notice:40] [2025-01-15 07:43:53.23 UTC] Chain extended, new tip: ed6b3331cda251028ccae685b8d8141ba24ef09299252eeafd005900070692cd at slot 1620475
[872abc84:cardano.node.ChainDB:Notice:40] [2025-01-15 07:43:53.24 UTC] Chain extended, new tip: 186608ce8ea4417075b2e0f754884672e9433cb3c0aadac81184ead741353505 at slot 1620476
[872abc84:cardano.node.ChainDB:Notice:40] [2025-01-15 07:43:53.24 UTC] Chain extended, new tip: 7ced6ab8d147a80b21cdb3ff286a379773055f2d14890bbf693bdc2052d51c5a at slot 1620477
[872abc84:cardano.node.ChainDB:Notice:40] [2025-01-15 07:43:53.24 UTC] Chain extended, new tip: 5807130c180f6fbf42c78bd67aa132f278922e86f6de6faa3c134610730f74e3 at slot 1620478
[872abc84:cardano.node.ChainDB:Notice:40] [2025-01-15 07:43:53.25 UTC] Chain extended, new tip: 5514e58f09c535e89ce6517c1deb206d9fd79880867b8259c8568f8b88c3fc92 at slot 1620479
[872abc84:cardano.node.ChainDB:Notice:40] [2025-01-15 07:43:53.25 UTC] Chain extended, new tip: 831ffd11b4e7668a91244e580d4946b010e0e08939297ca22abcef11fa838db0 at slot 1620480
[872abc84:cardano.node.ChainDB:Notice:40] [2025-01-15 07:43:53.25 UTC] Chain extended, new tip: 72e3f0a6b572b27a0681a201a1b975483cfc06ecd7fa0a0c76c156b960001c84 at slot 1620481
[872abc84:cardano.node.ChainDB:Notice:40] [2025-01-15 07:43:54.50 UTC] Chain extended, new tip: 0e211d04ef990564277e7f20cb914272c3d093269df654f40a2a3a44c29134b1 at slot 1621960

and these are the cardanofoundation/cardano-rosetta-java-api:main, its looking normal and keeps flowing

2025-01-15T07:43:31.058Z  INFO 1 --- [nio-8082-exec-5] o.c.r.a.n.service.NetworkServiceImpl     : [networkOptions] Looking for networkOptions
2025-01-15T07:43:56.718Z  INFO 1 --- [nio-8082-exec-7] o.c.r.a.n.service.NetworkServiceImpl     : [networkStatus] Looking for latest block
2025-01-15T07:43:56.719Z  INFO 1 --- [nio-8082-exec-7] o.c.r.a.n.service.NetworkServiceImpl     : [networkStatus] Looking for latest block
Hibernate: 
    select
        be1_0.hash,
        be1_0.body_size,
        be1_0.block_time,
        be1_0.epoch,
        be1_0.no_of_txs,
        be1_0.number,
        be1_0.prev_hash,
        be1_0.slot,
        be1_0.slot_leader 
    from
        block be1_0 
    order by
        be1_0.number desc 
    fetch
        first 1 rows only
2025-01-15T07:44:01.119Z  INFO 1 --- [nio-8082-exec-8] o.c.r.a.n.service.NetworkServiceImpl     : [networkOptions] Looking for networkOptions
2025-01-15T07:44:16.922Z  INFO 1 --- [io-8082-exec-10] o.c.r.a.n.service.NetworkServiceImpl     : [networkStatus] Looking for latest block
2025-01-15T07:44:16.922Z  INFO 1 --- [io-8082-exec-10] o.c.r.a.n.service.NetworkServiceImpl     : [networkStatus] Looking for latest block
Hibernate: 
    select
        be1_0.hash,
        be1_0.body_size,
        be1_0.block_time,
        be1_0.epoch,
        be1_0.no_of_txs,
        be1_0.number,
        be1_0.prev_hash,
        be1_0.slot,
        be1_0.slot_leader 
    from
        block be1_0 
    order by
        be1_0.number desc 
    fetch
        first 1 rows only
@dev-dantealighieri dev-dantealighieri added the bug Something isn't working label Jan 15, 2025
@Kammerlo
Copy link
Member

Hi, which release are you currently using?
We had an issue with regarding the indexer which was fixed in release 1.14
This issue was related to a stop of the indexer.

@Kammerlo Kammerlo self-assigned this Jan 15, 2025
@dev-dantealighieri
Copy link
Author

hi,

im using the latest version, i just cloned the repository and ran the indexer

docker ps
CONTAINER ID   IMAGE                                                 COMMAND                  CREATED          STATUS                    PORTS                                       NAMES
9e484a0db45a   ghcr.io/intersectmbo/cardano-submit-api:10.1.4        "/nix/store/zvv1ahld…"   13 minutes ago   Up 13 minutes             0.0.0.0:8090->8090/tcp, :::8090->8090/tcp   cardano-rosetta-java-cardano-submit-api-1
d5853d80e9e6   cardanofoundation/cardano-rosetta-java-indexer:main   "java -jar /app/yaci…"   13 minutes ago   Up 13 minutes                                                         cardano-rosetta-java-yaci-indexer-1
f6da3bd49277   ghcr.io/intersectmbo/cardano-node:10.1.4              "cardano-node run --…"   13 minutes ago   Up 13 minutes             0.0.0.0:3001->3001/tcp, :::3001->3001/tcp   cardano-rosetta-java-cardano-node-1
6535482a6093   postgres:14.11-bullseye                               "docker-entrypoint.s…"   13 minutes ago   Up 13 minutes (healthy)   0.0.0.0:5432->5432/tcp, :::5432->5432/tcp   cardano-rosetta-java-db-1
ef8b7180fdb3   cardanofoundation/cardano-rosetta-java-api:main       "java -jar /app/api.…"   13 minutes ago   Up 13 minutes (healthy)   0.0.0.0:8082->8082/tcp, :::8082->8082/tcp   cardano-rosetta-java-api-1
d296a94d8643   prom/node-exporter:v1.8.2                             "/bin/node_exporter …"   20 hours ago     Up 20 hours               0.0.0.0:9100->9100/tcp, :::9100->9100/tcp   node-exporter

im on this commit

* 28bcfa66 - (HEAD -> main, tag: 1.1.5, origin/main, origin/HEAD) chore:bump node to 10.1.4 (#268) (6 days ago) <Thomas Kammerlocher>

@Kammerlo
Copy link
Member

It's normal that the indexer loses the connection from time to time, but it reconnects. But this isn't the case for you?

@dev-dantealighieri
Copy link
Author

I am trying to get the latest block via

curl --location 'http:/localhost/network/status' \
--header 'Content-Type: application/json' \
--data '{
    "network_identifier" : {
        "blockchain": "cardano",
        "network": "mainnet"
    }
}'

but sometimes the response is not changing until restarting, is it normal?

@Kammerlo
Copy link
Member

Kammerlo commented Jan 16, 2025 •
edited
Loading

The connection losses of the indexer shouldn't be too long and it should get the connection back without a restart.

Did the node already reached the tip?
if yes, then it's not normal that the indexer can't recover.
If no, then it's a known issue from the indexer we are using, that it crashes and can't recover when it is syncing simultaneously with the node.
In the dockerimage (which includes everything) I implemented a routine to start the indexer only if the node reached the tip to avoid these crashes. It's an open todo for docker compose.

A workaround for now would be to let the node reach the tip and then restart the indexer then all components will be running smoothly.

@dev-dantealighieri
Copy link
Author

thanks, its the no case, if you can create an issue and show what to do, someone might do it

@dev-dantealighieri
Copy link
Author

also i dont understand why node stops syncing when idnexer stops? i dont understand why but when i restart it continues from where its left

@Kammerlo
Copy link
Member

In the docker compose not-reached-the-tip state the node should not stop. Just the indexer.

@dev-dantealighieri
Copy link
Author

i just realized my node has stopped, latest logs from it are like hits

[fa5b482f:cardano.node.ChainDB:Notice:192] [2025-01-16 21:48:36.44 UTC] Chain extended, new tip: 4a404765aef6a0b35467f8a15f0e9659f972dcdd79b43a1f4ff05e1aeed6c49e at slot 77656783
[fa5b482f:cardano.node.ChainDB:Info:192] [2025-01-16 21:48:36.66 UTC] Valid candidate 0e0f79aec1f2f46bade7ae807b49e6555bde05e27a3b9ff8370eabe6f6c7a1c6 at slot 77656839
[fa5b482f:cardano.node.ChainDB:Notice:192] [2025-01-16 21:48:36.66 UTC] Chain extended, new tip: 0e0f79aec1f2f46bade7ae807b49e6555bde05e27a3b9ff8370eabe6f6c7a1c6 at slot 77656839
[fa5b482f:cardano.node.ChainDB:Info:192] [2025-01-16 21:48:36.90 UTC] Valid candidate 2d4cc1e61d46de5cc07af5a94fe956d7fa4ddbd3523a942925fded5fcf130fac at slot 77656850
[fa5b482f:cardano.node.ChainDB:Notice:192] [2025-01-16 21:48:36.90 UTC] Chain extended, new tip: 2d4cc1e61d46de5cc07af5a94fe956d7fa4ddbd3523a942925fded5fcf130fac at slot 77656850
[fa5b482f:cardano.node.ChainDB:Info:192] [2025-01-16 21:48:37.15 UTC] Valid candidate 5ce6bacc68b83c962e6496cbcae8a370ad6b0a6851b95b5251864d5f93b6ca28 at slot 77656870
[fa5b482f:cardano.node.ChainDB:Notice:192] [2025-01-16 21:48:37.15 UTC] Chain extended, new tip: 5ce6bacc68b83c962e6496cbcae8a370ad6b0a6851b95b5251864d5f93b6ca28 at slot 77656870
[fa5b482f:cardano.node.ChainDB:Info:192] [2025-01-16 21:48:37.45 UTC] Valid candidate 750ba887100cee9a9125a21b9c0721767b837185612200965bb7683119244553 at slot 77656908
[fa5b482f:cardano.node.ChainDB:Notice:192] [2025-01-16 21:48:37.45 UTC] Chain extended, new tip: 750ba887100cee9a9125a21b9c0721767b837185612200965bb7683119244553 at slot 77656908

i cant see any problem, is this related to resources or something like that?

@Kammerlo
Copy link
Member

I assume you started to restart the node? Are there any logs, which might help, since out of the logs you shared I can't come up with an issue?

@dev-dantealighieri
Copy link
Author

nope, this is the last log it printed before dying, anyways i stopped and restarted the docker-compose everytime the node stopped and its synced now

also there was a worse issue 😄 my ram was getting full after sometime while syncing, was that normal? it was using the whole 128gb ram and swap

@Kammerlo
Copy link
Member

Hm no that is not normal, do you know which container filled the RAM?

@dev-dantealighieri
Copy link
Author

yeah, cardano node was %93, yaci indexer was %3 😄

as i said, after synchronization its all fine, im just telling you this to detect a potential memory leak

@Kammerlo
Copy link
Member

We will observe this and if it's an issue I will report it to the Cardano Node team. I will close this issue now, if you need anything else let me know.

The issue with the indexer is reported to the dev.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Kammerlo Kammerlo

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Kammerlo @dev-dantealighieri