Shulou(Shulou.com)06/01 Report--

[guest scene]

Now the customer carries on the online transaction directly through the driver, and the oid or unique key value will be printed to the business system log during the transaction. The transaction is successful in the actual transaction, but sometimes the transaction is slow. If you can locate the data node directly, you can check the log directly to the corresponding log entry. Then analyze the reasons for the slow down.

[question]

How to locate the data node on which the record is stored through the oid value?

[solution]

1. Oid is a 12-byte BSON object that consists of:

4-byte timestamp accurate to seconds

3-byte system (physical machine) marking

2-byte process ID

3-byte sequence number starting with a random number

two。 You cannot just pass the oid value to determine which data node the record falls on. If oid is a partition key, in the case of automatic segmentation, the data node where the record is located can be inferred combined with the partition information. In this case, you can use the following tool to confirm the data node where the record is located: sdbshard.tar.gz, download address:

Http://pmr.sequoiadb.com:8090/download/attachments/13205507/sdbshard.tar.gz?version=1&modificationDate=1507796046000&api=v2

[reference materials]

Oid definition: http://doc.sequoiadb.com/cn/SequoiaDB-cat_id-1519612292-edition_id-0

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.