Skip to main content



Spring MongoDB Log Connection Pool Details - Active, Used, Waiting

 

We couldn't find any direct way to log Mongo Connection pool Size. So, we did implement an indirect way as below. 

This may be incorrect at times when dealing with Sharded MongoDB having Primaty & Secondary nodes. Because, connection may be used based on read prefrence - Primary, primaryPreferred, Secondary, etc.

But, this gives an understanding if connections are used efficiently and there is no wait to acquire connections from pool. This can be further enhanced to log correct connection pool statistics. 


1) Implement MyConnectionPoolListener  as below - 

import java.util.concurrent.atomic.AtomicInteger;

import org.slf4j.Logger;

import org.slf4j.LoggerFactory;

import com.mongodb.event.ConnectionCheckOutFailedEvent;

import com.mongodb.event.ConnectionCheckOutStartedEvent;

import com.mongodb.event.ConnectionCheckedInEvent;

import com.mongodb.event.ConnectionCheckedOutEvent;

import com.mongodb.event.ConnectionClosedEvent;

import com.mongodb.event.ConnectionCreatedEvent;

import com.mongodb.event.ConnectionPoolListener;


/**

 * Connection pool listener

 */

public class MyConnectionPoolListener implements ConnectionPoolListener {

private final AtomicInteger size = new AtomicInteger();

private final AtomicInteger checkedOutCount = new AtomicInteger();

private final AtomicInteger waitQueueSize = new AtomicInteger();

private Logger logger = LoggerFactory.getLogger(MyConnectionPoolListener.class);


/**

* Get Total number of Connections

* @return

*/

public int getSize() {

return size.get();

}


/**

* Get number of connections checkedOut or are in use

* @return

*/

public int getCheckedOutCount() {

return checkedOutCount.get();

}

/**

* Get Wait Queue Size

* @return

*/

public int getWaitQueueSize() {

return waitQueueSize.get();

}


@Override

public void connectionCheckedOut(final ConnectionCheckedOutEvent event) {

int v = checkedOutCount.incrementAndGet();

int p = waitQueueSize.decrementAndGet();

logger.debug("connectionCheckedOut ID [{}], Active Count [{}], Wait Queue Size [{}]", event.getConnectionId().getServerId(), v, p);

}


@Override

public void connectionCheckedIn(final ConnectionCheckedInEvent event) {

int v = checkedOutCount.decrementAndGet();

logger.debug("connectionCheckedIn ID [{}], Active Count [{}]", event.getConnectionId().getServerId(), v);

}


@Override

public void connectionCreated(final ConnectionCreatedEvent event) {

int v = size.incrementAndGet();

logger.debug("connectionCreated ID [{}], Total Size [{}]", event.getConnectionId().getServerId(), v);

}


@Override

public void connectionClosed(final ConnectionClosedEvent event) {

int v = size.decrementAndGet();

logger.debug("connectionClosed ID [{}], Total Size [{}]", event.getConnectionId().getServerId(), v);

}


@Override

public void connectionCheckOutFailed(ConnectionCheckOutFailedEvent event) {

int v  = waitQueueSize.decrementAndGet();

logger.debug("connectionCheckOutFailed ID [{}], Wait Queue Size [{}]", event.getServerId(), v);

}

@Override

public void connectionCheckOutStarted(ConnectionCheckOutStartedEvent event) {

int v =  waitQueueSize.incrementAndGet();

logger.debug("connectionCheckOutFailed ID [{}], Wait Queue Size [{}]", event.getServerId(), v);

}

}


2) Implement MongoConfig  as below - 

import static org.bson.codecs.configuration.CodecRegistries.fromProviders;

import static org.bson.codecs.configuration.CodecRegistries.fromRegistries;


import org.bson.codecs.configuration.CodecRegistry;

import org.bson.codecs.pojo.PojoCodecProvider;

import org.springframework.boot.autoconfigure.mongo.MongoClientSettingsBuilderCustomizer;

import org.springframework.context.annotation.Bean;

import org.springframework.stereotype.Component;


import com.mongodb.MongoClientSettings;


import io.micrometer.core.instrument.MeterRegistry;

import io.micrometer.core.instrument.binder.mongodb.MongoMetricsCommandListener;


@Component

public class MongoConfig {


private MyConnectionPoolListener myCpL = new MyConnectionPoolListener();


public final CodecRegistry pojoCodecRegistry = fromRegistries(MongoClientSettings.getDefaultCodecRegistry(),

fromProviders(PojoCodecProvider.builder().automatic(true).build()));


@Bean

public MongoClientSettingsBuilderCustomizer mongoClientSettingsBuilderCustomizer(MeterRegistry meterRegistry) {

return builder -> builder.addCommandListener(new MongoMetricsCommandListener(meterRegistry))

.applyToConnectionPoolSettings(block -> block.addConnectionPoolListener(myCpL));

}


public MyConnectionPoolListener getMyCpL() {

return myCpL;

}

}


3) Create PoolMonitor  as below - 

import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import org.springframework.scheduling.annotation.EnableScheduling;
import org.springframework.scheduling.annotation.Scheduled;
import org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor;
import org.springframework.stereotype.Component;

@Component
@EnableScheduling
public class PoolMonitor {
public Logger logger = LoggerFactory.getLogger(PoolMonitor.class);
private final MongoConfig mongoConfig;
public PoolMonitor(MongoConfig mongoConfig) {
this.mongoConfig = mongoConfig;
}
@Scheduled(fixedDelay = 20000)
public void monitor() {
MyConnectionPoolListener myConnectionPoolListener = mongoConfig.getMyCpL();
logger.info("MongoDB Created Connection Pool Size [{}], Active Used Connection [{}], Wait Queue Size [{}]",
myConnectionPoolListener.getSize(), myConnectionPoolListener.getCheckedOutCount(), myConnectionPoolListener.getWaitQueueSize());
}
}


Pool Monitor will print status of MongoDB Connection Pool every 20 seconds. When someone uses MongoTemplate it will inturn take connections from pool but will increment or decrement Atomic Integer in Pool Listener. Thus, ensuring to print connection pool statistics. 




Comments

Popular posts

Unix Server ( Edge Node ) hangs when there are many jobs running on hadoop cluster started from Unix Edge Node.

  When a unix server or an edge node is running lots of jobs (like Spark, Hadoop, or custom batch processes), crashes happen. For example. For example a process might hit a segementation fault, memory issue or ay other runtime issue. By default, if ulimit -c is not 0, the OS will create core dump. Core dump are written to disk and can be very large, sometimes hundreds of MBs or even GBs per process. What we realized was that when multiple processes crash at the same time, the system suddenly tries to write core files to disk. This was leading to DisK I/O spikes. Thus, node was becoming unresponsive. This was also leading CPU spike because OS was handling crash logging. Setting "ulimit -c 0" disables core dumps. This way we lose ability to debug crashes via core dump But, kept production edge nodes stable. On most Linux systems, by default, "core dumps" are written in current working directory of the process that crashes. Linux allows you to change core dump file nam...




VPN testing checklist

 To test: Is VPN active? Is it leaking? Does it look residential? Does it alter network fingerprints? Public IP Test (Basic Detection) - curl ipinfo.io DNS Leak Test - nslookup google.com MTU Test (Encapsulation Detection) - ping 8.8.8.8 -f -l 1472 TCP MSS Inspection - Use Wireshark and Look for SYN packets. Traceroute Path Test - tracert 8.8.8.8 WebRTC Leak Test - browserleaks.com/webrtc IPv6 Leak Test - test-ipv6.com Latency / Jitter Test - ping -n 50 8.8.8.8. VPN usually causes: More Jitters and Latency. Reverse DNS (PTR Record) - nslookup <your-public-ip> IP Reputation Check - Like most IP's from VPN Providers like Express VPN, etc. are blacklisted and all. Look for: Proxy/VPN classification, Hosting provider tagging




Spark-JDBC connection with Oracle Fails - java.sql.SQLSyntaxErrorException: ORA-00903: invalid table name

  While connecting Spark with Oracle JDBC, one may observe exception like below -  spark.read.format("jdbc"). option("url", "jdbc:oracle:thin:@//oraclehost:1521/servicename"). option("dbtable", "mytable"). option("user", "myuser").option("driver", "oracle.jdbc.driver.OracleDriver") option("password", "mypassword"). load().write.parquet("/data/out") java.sql.SQLSyntaxErrorException: ORA-00903: invalid table name at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:447) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396) at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:951) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:513) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:227) at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:208) ...




Spring MongoDB Rest API not returning response in 90 seconds which is leading to client timeout

  We have Spring Boot  Rest API deployed in Kubernetes cluster which integrates with MongoDB to fetch the data.  MongoDB is fed with data by a real time Spark & NiFi job.  Our clients complained that for a request what they send they don't have response within 90 seconds. Consider it like an OMS ( Order ManagEment System).  On further analysis, we found that Spark & NiFi processing is happenning within 10 seconds after consuming response data from Kafka. Thus, initally out thought was that it due to delay from upstream to produce data in to Kafka.  Thankfully, our data had create / request  timestamp, and when response was received, and when response was inserted into MongoDB. Subtracting response insert time from request time seemed to be well within 90 seconds. But, still client did timeout on not seeing a response within 90 seconds. This led to confusion on our side.  But, then we realized it was due to Read Preference . We updated this...




MongoDB Regex Query taking more time in Production but same query perform well in UAT

   We came across a situation where-in, MongoDB Query was taking more time in Production like 10 seconds and 4.2 seconds but same query performed well in UAT taking under 400 ms. The very first thought that was evident to us that it is because of amount of data which differed in UAT and Production. Then we ran following to see the execution plan -   db.collection.aggregate(<queries>).explain() This gave us Winning and Rejected Plans. Under which, we analyzed that although it was using 'IXSCAN.' But, it was incorrect index- as we had one compound index built on time field and other fields, and there was other index just on time field for TTL purposes. Winning plan picked TTL index rather than compound index. Thus, we dropped TTL index and built TTL index on a different time field.  That got our query performance time from 10 seconds to 726 ms. Also, for other query the performance came down from 8 seconds to 4.3 seconds. Then, we ran following -  ...