The sink-connector lightweight stops replicating #380

aadant · 2023-11-17T16:26:19Z

last log before it stops :

154629410 2023-11-16 22:27:30.332 [pool-15502-thread-5] INFO com.altinity.clickhouse.sink.connector.db.DbWriter  - *************** EXECUTED BATCH Successfully Records: 12************** task(0) Thread ID: pool-15502-thread-5
Nov 16, 2023 10:29:15 PM com.github.shyiko.mysql.binlog.BinaryLogClient$5 run
INFO: Keepalive: Trying to restore lost connection to dbl1:3306

Restarting the container fixes the issue.

The text was updated successfully, but these errors were encountered:

subkanthi · 2023-11-21T18:03:10Z

Steps to reproduce:
Stop MySQL server when sink connector is already running and replicating,
The exception is not handled.

aadant · 2023-11-27T06:44:52Z

The issue comes from here https://github.com/shyiko/mysql-binlog-connector-java/blob/dd710a5466381faa57442977b24fceff56a0820e/src/main/java/com/github/shyiko/mysql/binlog/BinaryLogClient.java#L830

aadant · 2023-11-27T06:56:12Z

I suspect that there is a deadlock and that the connection waits forever to close. This can be confirmed by a java thread dump.

The solution found for such a situation is to restart debezium when no changes are detected for a while :
airbytehq/airbyte@e48492e

aadant · 2023-11-27T22:37:52Z

see also osheroff/mysql-binlog-connector-java#86

subkanthi · 2023-11-27T22:40:50Z

Store the timestamp of the last record and if its more than 5/10 mins then restart Debezium Engine.

aadant · 2023-11-29T02:50:58Z

root cause traced to this issue osheroff/mysql-binlog-connector-java#133 (reporter)

aadant · 2023-12-01T03:41:49Z

looks like a OpenJDK 11 bug, @subkanthi let us upgrade !

aadant · 2023-12-08T00:37:34Z

Reproduced with OpenJDK 17 see osheroff/mysql-binlog-connector-java#133

aadant · 2023-12-24T00:19:18Z

The problem continues after the fix ...

subkanthi · 2024-01-12T19:15:09Z

From analyzing the thread dump provided, the cause seems to be because of high number of GC threads

 There are 179 Garbage Collection(GC) Threads. This is a very high number of GC Threads. It may affect the application's performance. You may consider reducing GC threads.

https://blog.fastthread.io/2015/09/02/thread-dump-analysis-pattern-several-scavengers/

As shown in the image there are only 15 threads that are created by sink connector

subkanthi · 2024-01-12T20:01:49Z

There are also 19 threads that are blocked in TIMED_WAITING state

main
PRIORITY : 5

THREAD ID : 0X00007FFFF0024C40

NATIVE ID : 0X7

NATIVE ID (DECIMAL) : 7

STATE : TIMED_WAITING


stackTrace:
java.lang.Thread.State: TIMED_WAITING (parking)
at jdk.internal.misc.Unsafe.park(java.base@17.0.2/Native Method)
- parking to wait for <0x00007fdfd03b7508> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.parkNanos(java.base@17.0.2/LockSupport.java:252)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(java.base@17.0.2/AbstractQueuedSynchronizer.java:1757)
at io.debezium.connector.base.ChangeEventQueue.poll(ChangeEventQueue.java:275)
at io.debezium.connector.mysql.MySqlConnectorTask.doPoll(MySqlConnectorTask.java:239)
at io.debezium.connector.common.BaseSourceTask.poll(BaseSourceTask.java:180)
at io.debezium.embedded.EmbeddedEngine.pollRecords(EmbeddedEngine.java:695)
at io.debezium.embedded.EmbeddedEngine.run(EmbeddedEngine.java:475)
at io.debezium.embedded.ConvertingEngineBuilder$2.run(ConvertingEngineBuilder.java:229)
at com.altinity.clickhouse.debezium.embedded.cdc.DebeziumChangeEventCapture.setupDebeziumEventCapture(DebeziumChangeEventCapture.java:483)
at com.altinity.clickhouse.debezium.embedded.cdc.DebeziumChangeEventCapture.setup(DebeziumChangeEventCapture.java:512)
at com.altinity.clickhouse.debezium.embedded.ClickHouseDebeziumEmbeddedApplication.start(ClickHouseDebeziumEmbeddedApplication.java:212)
at com.altinity.clickhouse.debezium.embedded.ClickHouseDebeziumEmbeddedApplication.main(ClickHouseDebeziumEmbeddedApplication.java:88)

subkanthi · 2024-01-16T20:07:29Z

https://docs.oracle.com/en/java/javase/17/gctuning/parallel-collector1.html#GUID-5A7866BE-59DF-44AD-B51A-274DE3F2BF59

subkanthi · 2024-02-07T19:30:42Z

Workaround Solution:
These two configuration variables restart.event.loop and restart.event.loop.timeout.period.secs define the restart logic.
The debezium event loop will be restarted when the last timestamp of the record received exceeds the restart.event.loop.timeout.period.secs

Also the debezium event loop is restarted when the timestamp of the record stored in altinity_sink_connector.replica_source_info exceeds the threshold.

Selfeer · 2024-02-26T19:18:39Z

The issue was manually verified by the Altinity QA team and marked as qa-verified.

Build used for testing: altinityinfra/clickhouse-sink-connector:464-c979a8c2583ff701dd5b63efb8f36f7fff8111e7-lt

We've verified that setting restart.event.loop to true and specifying seconds values in restart.event.loop.timeout.period.secs configuration results in a CDC event loop restart with a corresponding log message being shown when the timeout is reached.

Values specified in restart.event.loop.timeout.period.secs configuration are respected. The usage of these configurations doesn't seem to break any other clickhouse-sink-connector-lightweight functionality.

aadant · 2024-04-01T18:13:20Z

@subkanthi a workaround is in place but this still impacts the sink-connector latency (up to restart.event.loop.timeout.period.secs), IMHO the root cause should be chased down with Debezium folks and possibly the binary log library they use.

subkanthi · 2024-04-02T16:08:16Z

Analyzing the latest thread dump, all the 8 threads in change-event-source-coordinator are in TIMED_WAITING state.

debezium-mysqlconnector-embeddedconnector-change-event-source-coordinator
PRIORITY : 5

THREAD ID : 0X00007FDDF07899B0

NATIVE ID : 0X10A

NATIVE ID (DECIMAL) : 266

STATE : TIMED_WAITING


stackTrace:
java.lang.Thread.State: TIMED_WAITING (parking)
at jdk.internal.misc.Unsafe.park(java.base@17.0.2/Native Method)
- parking to wait for <0x00007fdfd04475f0> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.parkNanos(java.base@17.0.2/LockSupport.java:252)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(java.base@17.0.2/AbstractQueuedSynchronizer.java:1672)
at java.util.concurrent.ThreadPoolExecutor.awaitTermination(java.base@17.0.2/ThreadPoolExecutor.java:1464)
at java.util.concurrent.Executors$DelegatedExecutorService.awaitTermination(java.base@17.0.2/Executors.java:743)
at com.github.shyiko.mysql.binlog.BinaryLogClient.awaitTerminationInterruptibly(BinaryLogClient.java:1337)
at com.github.shyiko.mysql.binlog.BinaryLogClient.terminateKeepAliveThread(BinaryLogClient.java:1329)
at com.github.shyiko.mysql.binlog.BinaryLogClient.disconnect(BinaryLogClient.java:1314)
at io.debezium.connector.mysql.MySqlStreamingChangeEventSource.execute(MySqlStreamingChangeEventSource.java:1001)
at io.debezium.connector.mysql.MySqlStreamingChangeEventSource.execute(MySqlStreamingChangeEventSource.java:74)
at io.debezium.pipeline.ChangeEventSourceCoordinator.streamEvents(ChangeEventSourceCoordinator.java:272)
at io.debezium.pipeline.ChangeEventSourceCoordinator.executeChangeEventSources(ChangeEventSourceCoordinator.java:197)
at io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:137)
at io.debezium.pipeline.ChangeEventSourceCoordinator$$Lambda$727/0x00000008010f77b8.run(Unknown Source)
at java.util.concurrent.Executors$RunnableAdapter.call(java.base@17.0.2/Executors.java:539)
at java.util.concurrent.FutureTask.run(java.base@17.0.2/FutureTask.java:264)
at java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@17.0.2/ThreadPoolExecutor.java:1136)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(java.base@17.0.2/ThreadPoolExecutor.java:635)
at java.lang.Thread.run(java.base@17.0.2/Thread.java:833)

subkanthi · 2024-04-02T16:10:59Z

Similar issue in debezium zulipchat
https://debezium.zulipchat.com/#narrow/stream/348104-community-mysql/topic/2.2E5.2E1.2C.20stuck.20indefinitely.20until.20connector.20restart

Alexandru Cristu
3:46 AM
seems to happen after we see this: com.github.shyiko.mysql.binlog.BinaryLogClient$5 run
INFO: Keepalive: Trying to restore lost connection to ...

Task thread is waiting in doPoll:

"task-thread-source_65afd9cf169951285b70c4a1-0" #79816 prio=5 os_prio=0 cpu=2977135.32ms elapsed=79038.87s tid=0x00007f69b4205540 nid=0x13922 waiting on condition  [0x00007f6958504000]
   java.lang.Thread.State: TIMED_WAITING (parking)
    at jdk.internal.misc.Unsafe.park(java.base@17.0.9/Native Method)
    - parking to wait for  <0x00000005ad829900> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
    at java.util.concurrent.locks.LockSupport.parkNanos(java.base@17.0.9/LockSupport.java:252)
    at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(java.base@17.0.9/AbstractQueuedSynchronizer.java:1757)
    at io.debezium.connector.base.ChangeEventQueue.poll(ChangeEventQueue.java:275)
    at io.debezium.connector.mysql.MySqlConnectorTask.doPoll(MySqlConnectorTask.java:252)
    at io.debezium.connector.common.BaseSourceTask.poll(BaseSourceTask.java:182)
    at org.apache.kafka.connect.runtime.AbstractWorkerSourceTask.poll(AbstractWorkerSourceTask.java:469)
    at org.apache.kafka.connect.runtime.AbstractWorkerSourceTask.execute(AbstractWorkerSourceTask.java:357)
    at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:204)
    at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:259)
    at org.apache.kafka.connect.runtime.AbstractWorkerSourceTask.run(AbstractWorkerSourceTask.java:77)
    at org.apache.kafka.connect.runtime.isolation.Plugins.lambda$withClassLoader$1(Plugins.java:181)
    at org.apache.kafka.connect.runtime.isolation.Plugins$$Lambda$953/0x00007f6a65b1cc50.run(Unknown Source)
    at java.util.concurrent.Executors$RunnableAdapter.call(java.base@17.0.9/Executors.java:539)
    at java.util.concurrent.FutureTask.run(java.base@17.0.9/FutureTask.java:264)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@17.0.9/ThreadPoolExecutor.java:1136)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(java.base@17.0.9/ThreadPoolExecutor.java:635)
    at java.lang.Thread.run(java.base@17.0.9/Thread.java:840)
The "change-event-source-coordinator" thread is stuck in BinaryLogClient.disconnect, which in turn is stuck waiting for the keepalive thread to finish:

"debezium-mysqlconnector-source_65afd9cf169951285b70c4a1-change-event-source-coordinator" #397 prio=5 os_prio=0 cpu=63726.27ms elapsed=482672.61s tid=0x00007f6a54458510 nid=0x1fd waiting on condition  [0x00007f6961e9c000]
   java.lang.Thread.State: TIMED_WAITING (parking)
        at jdk.internal.misc.Unsafe.park(java.base@17.0.9/Native Method)
        - parking to wait for  <0x000000050c001a90> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
        at java.util.concurrent.locks.LockSupport.parkNanos(java.base@17.0.9/LockSupport.java:252)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(java.base@17.0.9/AbstractQueuedSynchronizer.java:1672)
        at java.util.concurrent.ThreadPoolExecutor.awaitTermination(java.base@17.0.9/ThreadPoolExecutor.java:1464)
        at java.util.concurrent.Executors$DelegatedExecutorService.awaitTermination(java.base@17.0.9/Executors.java:743)
        at com.github.shyiko.mysql.binlog.BinaryLogClient.awaitTerminationInterruptibly(BinaryLogClient.java:1337)
        at com.github.shyiko.mysql.binlog.BinaryLogClient.terminateKeepAliveThread(BinaryLogClient.java:1329)
        at com.github.shyiko.mysql.binlog.BinaryLogClient.disconnect(BinaryLogClient.java:1314)
        at io.debezium.connector.mysql.MySqlStreamingChangeEventSource.execute(MySqlStreamingChangeEventSource.java:1001)
        at io.debezium.connector.mysql.MySqlStreamingChangeEventSource.execute(MySqlStreamingChangeEventSource.java:74)
        at io.debezium.pipeline.ChangeEventSourceCoordinator.streamEvents(ChangeEventSourceCoordinator.java:272)
        at io.debezium.pipeline.ChangeEventSourceCoordinator.executeChangeEventSources(ChangeEventSourceCoordinator.java:197)
        at io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:137)
        at io.debezium.pipeline.ChangeEventSourceCoordinator$$Lambda$1777/0x00007f6a660beac0.run(Unknown Source)
        at java.util.concurrent.Executors$RunnableAdapter.call(java.base@17.0.9/Executors.java:539)
        at java.util.concurrent.FutureTask.run(java.base@17.0.9/FutureTask.java:264)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@17.0.9/ThreadPoolExecutor.java:1136)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(java.base@17.0.9/ThreadPoolExecutor.java:635)
        at java.lang.Thread.run(java.base@17.0.9/Thread.java:840)
The keepalive thread is stuck waiting for SSLSocket to close:

"blc-keepalive-production-aurora-80-cluster.cluster-cfqdxwvdz9bt.us-east-1.rds.amazonaws.com:3306" #401 prio=5 os_prio=0 cpu=56.99ms elapsed=569119.58s tid=0x00007f69d8079dc0 nid=0x201 waiting on condition  [0x00007f69624a3000]
   java.lang.Thread.State: WAITING (parking)
    at jdk.internal.misc.Unsafe.park(java.base@17.0.9/Native Method)
    - parking to wait for  <0x000000050c032238> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)
    at java.util.concurrent.locks.LockSupport.park(java.base@17.0.9/LockSupport.java:211)
    at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(java.base@17.0.9/AbstractQueuedSynchronizer.java:715)
    at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(java.base@17.0.9/AbstractQueuedSynchronizer.java:938)
    at java.util.concurrent.locks.ReentrantLock$Sync.lock(java.base@17.0.9/ReentrantLock.java:153)
    at java.util.concurrent.locks.ReentrantLock.lock(java.base@17.0.9/ReentrantLock.java:322)
    at sun.security.ssl.SSLSocketImpl.closeNotify(java.base@17.0.9/SSLSocketImpl.java:735)
    at sun.security.ssl.TransportContext.closeNotify(java.base@17.0.9/TransportContext.java:287)
    at sun.security.ssl.TransportContext.initiateOutboundClose(java.base@17.0.9/TransportContext.java:598)
    at sun.security.ssl.TransportContext.closeOutbound(java.base@17.0.9/TransportContext.java:582)
    at sun.security.ssl.SSLSocketImpl.shutdownOutput(java.base@17.0.9/SSLSocketImpl.java:875)
    at com.github.shyiko.mysql.binlog.network.protocol.PacketChannel.close(PacketChannel.java:125)
    at com.github.shyiko.mysql.binlog.BinaryLogClient.disconnectChannel(BinaryLogClient.java:1361)
    at com.github.shyiko.mysql.binlog.BinaryLogClient.terminateConnect(BinaryLogClient.java:1345)
    at com.github.shyiko.mysql.binlog.BinaryLogClient.access$800(BinaryLogClient.java:96)
    at com.github.shyiko.mysql.binlog.BinaryLogClient$5.run(BinaryLogClient.java:894)
    at java.util.concurrent.Executors$RunnableAdapter.call(java.base@17.0.9/Executors.java:539)
    at java.util.concurrent.FutureTask.run(java.base@17.0.9/FutureTask.java:264)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@17.0.9/ThreadPoolExecutor.java:1136)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(java.base@17.0.9/ThreadPoolExecutor.java:635)
    at java.lang.Thread.run(java.base@17.0.9/Thread.java:840)
Restarting the connector caused streaming to resume, the above threads remain stuck. Restart is currently needed every few hours, but it seems to become more frequent, at some point will need to restart the JVM to clean up these leaked threads.

Investigating potentially related JDK issue https://bugs.openjdk.org/browse/JDK-8241239?focusedId=14646711&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-14646711

Any suggestions how to troubleshoot this further? Have you seen this before?

subkanthi · 2024-04-02T16:14:02Z

Debezium issue - https://issues.redhat.com/browse/DBZ-7570

subkanthi · 2024-04-02T17:38:06Z

said:

It's on my radar for 2.7.0.Alpha1
Thanks Chris, is there any workarounds for now, like mysql version change maybe as discussed in the other thread?

Chris Cranford (Naros): said:

Thanks Chris, is there any workarounds for now, like mysql version change maybe as discussed in the other thread?

Unfortunately nothing really at this time.

subkanthi · 2024-05-26T21:57:54Z

Even though debezium team addressed the issue in 2.7.0 https://issues.redhat.com/browse/DBZ-7570, they have introduced another bug
https://issues.redhat.com/browse/DBZ-7873

aadant · 2025-01-15T00:19:23Z

The issue is still present in https://github.com/Altinity/clickhouse-sink-connector/releases/tag/2.5.0

2025-01-14 23:04:33.044 INFO  - ***** BATCH marked as processed to debezium ****Binlog file:binary.159358 Binlog position: 493036955 GTID: -1 Sequence Number: 1736895874003003343 Debezium Timestamp: 1736895873003
Jan 14, 2025 11:06:06 PM com.github.shyiko.mysql.binlog.BinaryLogClient$5 run
INFO: Keepalive: Trying to restore lost connection to fpif1-firmdbl1:3306
2025-01-14 23:06:06.685 INFO  - Keepalive: Trying to restore lost connection to localhost:3306

aadant · 2025-01-15T00:38:04Z

see https://issues.redhat.com/browse/DBZ-7563
proposed workaround is

use.nongraceful.disconnect=true

aadant · 2025-01-15T21:48:55Z

use.nongraceful.disconnect=true

does not solve the issue

aadant · 2025-01-22T17:23:04Z

this setting works for us :

use.nongraceful.disconnect: "true"
database.keep.alive.interval.`ms: "30000"  #Send keepalive every 30 seconds
database.connection.reconnect.backoff.ms: "1000"
database.connection.reconnect.backoff.max.ms: "10000"
database.ssl.mode: "disabled"

#380 - Added configuration settings to prevent freeze of debezium loop.

aadant assigned subkanthi Nov 17, 2023

aadant added high-priority bug Something isn't working labels Nov 17, 2023

subkanthi added the GA-1 All the issues that are issues in release(Scheduled Dec 2023) label Dec 18, 2023

subkanthi mentioned this issue Dec 19, 2023

Updated debezium version to 2.5.0.Beta1 #414

Merged

subkanthi closed this as completed in #414 Dec 22, 2023

aadant reopened this Dec 24, 2023

subkanthi mentioned this issue Jan 16, 2024

Added logic to launch debezium event loop in a separate thread, set t… #436

Merged

subkanthi closed this as completed in #436 Jan 23, 2024

subkanthi reopened this Jan 24, 2024

Selfeer added the qa-verified label to mark issues that were verified by QA label Feb 26, 2024

subkanthi closed this as completed Feb 27, 2024

aadant reopened this Apr 1, 2024

svb-alt added the lightweight Issues related to Lightweight version label Apr 4, 2024

subkanthi added this to the 2.2.0 milestone May 26, 2024

subkanthi added the p1 label May 28, 2024

subkanthi mentioned this issue Jun 5, 2024

Upgrade to Debezium 2.7 failure #626

Closed

subkanthi added the debezium-2.7 label Jun 6, 2024

subkanthi modified the milestones: 2.2.0, 2.3.0 Jun 27, 2024

subkanthi mentioned this issue Jul 2, 2024

Sink connector stops replicating data and there are no log updates #665

Open

subkanthi removed this from the 2.2.0 milestone Jul 2, 2024

subkanthi added this to the 2.4.0 milestone Aug 28, 2024

aadant mentioned this issue Sep 15, 2024

MySQL Snapshot fails at 50m rows and keeps starting over and over again #812

Open

subkanthi modified the milestones: 2.4.0, 2.5.0 Oct 20, 2024

subkanthi modified the milestones: 2.5.0, 2.6.0 Nov 6, 2024

svb-alt removed the p1 label Jan 7, 2025

subkanthi added a commit that referenced this issue Jan 22, 2025

#380 - Added configuration settings to prevent freeze of debezium loop.

788f862

subkanthi mentioned this issue Jan 22, 2025

#380 - Added configuration settings to prevent freeze of debezium loop. #974

Merged

subkanthi added a commit that referenced this issue Jan 22, 2025

Merge pull request #974 from Altinity/disable_ssl_configuration

e217574

#380 - Added configuration settings to prevent freeze of debezium loop.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

The sink-connector lightweight stops replicating #380

The sink-connector lightweight stops replicating #380

aadant commented Nov 17, 2023

subkanthi commented Nov 21, 2023

aadant commented Nov 27, 2023

aadant commented Nov 27, 2023

aadant commented Nov 27, 2023

subkanthi commented Nov 27, 2023

aadant commented Nov 29, 2023

aadant commented Dec 1, 2023

aadant commented Dec 8, 2023

aadant commented Dec 24, 2023

subkanthi commented Jan 12, 2024 •

edited

Loading

subkanthi commented Jan 12, 2024

subkanthi commented Jan 16, 2024

subkanthi commented Feb 7, 2024

Selfeer commented Feb 26, 2024 •

edited

Loading

aadant commented Apr 1, 2024

subkanthi commented Apr 2, 2024

subkanthi commented Apr 2, 2024 •

edited

Loading

subkanthi commented Apr 2, 2024

subkanthi commented Apr 2, 2024 •

edited

Loading

subkanthi commented May 26, 2024

aadant commented Jan 15, 2025

aadant commented Jan 15, 2025

aadant commented Jan 15, 2025

aadant commented Jan 22, 2025

The sink-connector lightweight stops replicating #380

The sink-connector lightweight stops replicating #380

Comments

aadant commented Nov 17, 2023

subkanthi commented Nov 21, 2023

aadant commented Nov 27, 2023

aadant commented Nov 27, 2023

aadant commented Nov 27, 2023

subkanthi commented Nov 27, 2023

aadant commented Nov 29, 2023

aadant commented Dec 1, 2023

aadant commented Dec 8, 2023

aadant commented Dec 24, 2023

subkanthi commented Jan 12, 2024 • edited Loading

subkanthi commented Jan 12, 2024

subkanthi commented Jan 16, 2024

subkanthi commented Feb 7, 2024

Selfeer commented Feb 26, 2024 • edited Loading

aadant commented Apr 1, 2024

subkanthi commented Apr 2, 2024

subkanthi commented Apr 2, 2024 • edited Loading

subkanthi commented Apr 2, 2024

subkanthi commented Apr 2, 2024 • edited Loading

subkanthi commented May 26, 2024

aadant commented Jan 15, 2025

aadant commented Jan 15, 2025

aadant commented Jan 15, 2025

aadant commented Jan 22, 2025

subkanthi commented Jan 12, 2024 •

edited

Loading

Selfeer commented Feb 26, 2024 •

edited

Loading

subkanthi commented Apr 2, 2024 •

edited

Loading

subkanthi commented Apr 2, 2024 •

edited

Loading