I had a case at a customer recently where newly uploaded documents into Alfresco would always be searchable but only after 2min45s to 3min. The environment in question is an Alfresco Content Services 7.1 with High Availability (Repository and Share Clustering, Solr Sharding on multi-nodes, …) used for QA\/TEST. It’s an ongoing project to upgrade an Alfresco 6.1 to 7.1 and during the testing, the documents take time to be visible through searches, everything else works properly.<\/p>\n
<\/p>\n
Since there are a few similar environments on these exact same versions and setup, I tried to replicate the issue on two others but without success. On other instances, documents are searchable properly within the next 15 to 20s more or less, which is then expected based on the Solr Tracker schedule. No specific configurations were put that are out of the ordinary, it’s a rather straight forward setup that matches the previous one.<\/p>\n
<\/p>\n
Since it’s a new version (ACS 7.1 \/ ASS 2.0.2), I thought that maybe it could be linked to the Sharding methods or the number of Shards, even if it shouldn’t (except if there is a bug, of course). So, I did some tests to reduce the number of Shards, change the Sharding method as well as completely remove Sharding and going back to a standard Alfresco\/Archive cores setup. Here is an example of the main steps that can be used to remove the current Shards and create a unique new one for live documents:<\/p>\n
### Solr Node1 & Node2\n## Remove Solr Shards\n$ curl -v \"http:\/\/localhost:8983\/solr\/admin\/cores?action=removeCore&storeRef=workspace:\/\/SpacesStore&coreName=alfresco-0\"\n$ curl -v \"http:\/\/localhost:8983\/solr\/admin\/cores?action=removeCore&storeRef=workspace:\/\/SpacesStore&coreName=alfresco-1\"\n$ curl -v \"http:\/\/localhost:8983\/solr\/admin\/cores?action=removeCore&storeRef=workspace:\/\/SpacesStore&coreName=alfresco-2\"\n$ curl -v \"http:\/\/localhost:8983\/solr\/admin\/cores?action=removeCore&storeRef=archive:\/\/SpacesStore&coreName=archive-0\"\n## Stop Solr\n$ sudo systemctl stop solr.service\n## Cleanup config\n$ rm -rf $SOLR_HOME\/solrhome\/rerank--a*\n## Cleanup indexes\n$ ls $SOLR_DATA_HOME\/\ncontent index models\n$ rm -rf $SOLR_DATA_HOME\/*\/*\n## Start Solr\n$ sudo systemctl start solr.service\n## Create Solr Shard for alfresco-0\n$ solr_node_id=1 # for Solr Node2: solr_node_id=2\n$ range=25000000\n$ total_shards=20\n$ for shard_id in `seq 0 0`; do\n begin_range=$((${shard_id} * ${range}))\n end_range=$(((${shard_id} + 1) * ${range}))\n curl -v \"http:\/\/localhost:8983\/solr\/admin\/cores?action=newCore&storeRef=workspace:\/\/SpacesStore&numShards=${total_shards}&numNodes=${total_shards}&nodeInstance=${solr_node_id}&template=rerank&coreName=alfresco&shardIds=${shard_id}&property.shard.method=DB_ID_RANGE&property.shard.range=${begin_range}-${end_range}&property.shard.instance=${shard_id}\"\n echo \"\"\n echo \" --> Range N\u00b0${shard_id} created with: ${begin_range}-${end_range}\"\n echo \"\"\n sleep 2\n$ done<\/pre>\n <\/p>\n
After a full reindex, the behavior was the same, as we could expect. My next test would have been to try to revert to the previous Alfresco Search Services version (ASS 1.4.3) that was used but while doing the testing and checking the SUMMARY<\/strong> and REPORT<\/strong> generated by Solr (E.g.: http:\/\/localhost:8983\/solr\/admin\/cores?action=SUMMARY&core=alfresco-0<\/em>), I found it strange that the value of “Date for last TX on server” and “Last Index TX Commit Date” didn’t match the time when I uploaded my latest document on Alfresco, it was delayed… I deleted and re-uploaded the document again and saw the same thing, the time didn’t match. This could only be because of Operating System time that doesn’t match between the Solr and Alfresco\/DB servers.<\/p>\n <\/p>\n
What happened is that these servers do not have access to internet, and they weren’t set with an internal Time Server. The “systemd-timesyncd” service was enabled but it couldn’t synchronize the time because of that:<\/p>\n
root@solr_node1:~$ timedatectl status\n Local time: Mon 2021-12-13 12:35:34 UTC\n Universal time: Mon 2021-12-13 12:35:34 UTC\n RTC time: Mon 2021-12-13 12:38:05\n Time zone: Etc\/UTC (UTC, +0000)\n System clock synchronized: no\nsystemd-timesyncd.service active: yes\n RTC in local TZ: no\nroot@solr_node1:~$\nroot@solr_node1:~$ timedatectl set-ntp off\nroot@solr_node1:~$ timedatectl set-ntp on\nroot@solr_node1:~$\nroot@solr_node1:~$ systemctl restart systemd-timesyncd.service\nroot@solr_node1:~$\nroot@solr_node1:~$ systemctl status systemd-timesyncd.service\n\u25cf systemd-timesyncd.service - Network Time Synchronization\n Loaded: loaded (\/lib\/systemd\/system\/systemd-timesyncd.service; enabled; vendor preset: enabled)\n Active: active (running) since Mon 2021-12-13 12:38:55 UTC; 30s ago\n Docs: man:systemd-timesyncd.service(8)\n Main PID: 29451 (systemd-timesyn)\n Status: \"Connecting to time server 91.189.94.4:123 (ntp.ubuntu.com).\"\n Tasks: 2 (limit: 4915)\n CGroup: \/system.slice\/systemd-timesyncd.service\n \u2514\u250029451 \/lib\/systemd\/systemd-timesyncd\n\nDec 13 12:38:55 solr_node1 systemd[1]: Starting Network Time Synchronization...\nDec 13 12:38:55 solr_node1 systemd[1]: Started Network Time Synchronization.\nDec 13 12:39:05 solr_node1 systemd-timesyncd[29451]: Timed out waiting for reply from 91.189.91.157:123 (ntp.ubuntu.com).\nDec 13 12:39:15 solr_node1 systemd-timesyncd[29451]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com).\nroot@solr_node1:~$<\/pre>\n <\/p>\n
As a quick workaround, the time was manually synchronized:<\/p>\n
root@solr_node1:~$ date -s \"13 Dec 2021 12:41:16Z\"\nMon Dec 13 12:41:16 UTC 2021\nroot@solr_node1:~$<\/pre>\n <\/p>\n
Right after, the issue was gone, documents were searchable around 20s after the upload to Alfresco. Obviously, the long-term solution is to setup correctly the Operating System with the customer’s correct Time Servers. If they are blocking internet, they must probably have their dedicated Time Servers. For information, this is how to configure custom Time Servers on Ubuntu 18.04:<\/p>\n
root@solr_node1:~$ vi \/etc\/systemd\/timesyncd.conf\nroot@solr_node1:~$\nroot@solr_node1:~$ grep -v '^#' \/etc\/systemd\/timesyncd.conf\n[Time]\nNTP=ntp1.domain.com\nFallbackNTP=ntp2.domain.com\nroot@solr_node1:~$\nroot@solr_node1:~$ systemctl restart systemd-timesyncd.service\nroot@solr_node1:~$\nroot@solr_node1:~$ systemctl status systemd-timesyncd.service\n\u25cf systemd-timesyncd.service - Network Time Synchronization\n Loaded: loaded (\/lib\/systemd\/system\/systemd-timesyncd.service; enabled; vendor preset: enabled)\n Active: active (running) since Mon 2021-12-13 15:28:26 UTC; 15s ago\n Docs: man:systemd-timesyncd.service(8)\n Main PID: 29817 (systemd-timesyn)\n Status: \"Synchronized to time server 10.10.10.10:123 (ntp1.domain.com).\"\n Tasks: 2 (limit: 4915)\n CGroup: \/system.slice\/systemd-timesyncd.service\n \u2514\u250029817 \/lib\/systemd\/systemd-timesyncd\n\nDec 13 15:28:25 solr_node1 systemd[1]: Starting Network Time Synchronization...\nDec 13 15:28:26 solr_node1 systemd[1]: Started Network Time Synchronization.\nDec 13 15:28:35 solr_node1 systemd-timesyncd[29817]: Synchronized to time server 10.10.10.10:123 (ntp1.domain.com).\nroot@solr_node1:~$\nroot@solr_node1:~$ timedatectl\n Local time: Mon 2021-12-13 15:28:50 UTC\n Universal time: Mon 2021-12-13 15:28:50 UTC\n RTC time: Mon 2021-12-13 15:28:50\n Time zone: Etc\/UTC (UTC, +0000)\n System clock synchronized: yes\nsystemd-timesyncd.service active: yes\n RTC in local TZ: no\nroot@solr_node1:~$<\/pre>\n <\/p>\n","protected":false},"excerpt":{"rendered":"
I had a case at a customer recently where newly uploaded documents into Alfresco would always be searchable but only after 2min45s to 3min. The environment in question is an Alfresco Content Services 7.1 with High Availability (Repository and Share Clustering, Solr Sharding on multi-nodes, …) used for QA\/TEST. It’s an ongoing project to upgrade […]<\/p>\n","protected":false},"author":20,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197,525],"tags":[3169,91,123,124],"type_dbi":[],"class_list":["post-494","post","type-post","status-publish","format-standard","hentry","category-application-integration-middleware","category-enterprise-content-management","tag-alfresco","tag-index","tag-ntp","tag-slowness"],"acf":[],"yoast_head":"\n
Alfresco - Documents are searchable only after 3min - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/alfresco-documents-are-searchable-only-after-3min\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Alfresco - Documents are searchable only after 3min\" \/>\n<meta property=\"og:description\" content=\"I had a case at a customer recently where newly uploaded documents into Alfresco would always be searchable but only after 2min45s to 3min. The environment in question is an Alfresco Content Services 7.1 with High Availability (Repository and Share Clustering, Solr Sharding on multi-nodes, …) used for QA\/TEST. It’s an ongoing project to upgrade […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/alfresco-documents-are-searchable-only-after-3min\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2022-01-05T18:20:04+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-04-06T06:26:26+00:00\" \/>\n<meta name=\"author\" content=\"Morgan Patou\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@MorganPatou\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Morgan Patou\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/alfresco-documents-are-searchable-only-after-3min\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/alfresco-documents-are-searchable-only-after-3min\/\"},\"author\":{\"name\":\"Morgan Patou\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"headline\":\"Alfresco – Documents are searchable only after 3min\",\"datePublished\":\"2022-01-05T18:20:04+00:00\",\"dateModified\":\"2022-04-06T06:26:26+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/alfresco-documents-are-searchable-only-after-3min\/\"},\"wordCount\":498,\"commentCount\":0,\"keywords\":[\"Alfresco\",\"index\",\"NTP\",\"slowness\"],\"articleSection\":[\"Application integration & Middleware\",\"Enterprise content management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/alfresco-documents-are-searchable-only-after-3min\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/alfresco-documents-are-searchable-only-after-3min\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/alfresco-documents-are-searchable-only-after-3min\/\",\"name\":\"Alfresco - Documents are searchable only after 3min - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2022-01-05T18:20:04+00:00\",\"dateModified\":\"2022-04-06T06:26:26+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/alfresco-documents-are-searchable-only-after-3min\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/alfresco-documents-are-searchable-only-after-3min\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/alfresco-documents-are-searchable-only-after-3min\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Alfresco – Documents are searchable only after 3min\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\",\"name\":\"Morgan Patou\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g\",\"caption\":\"Morgan Patou\"},\"description\":\"Morgan Patou has over 12 years of experience in Enterprise Content Management (ECM) systems, with a strong focus in recent years on platforms such as Alfresco, Documentum, and M-Files. He specializes in the architecture, setup, customization, and maintenance of ECM infrastructures in complex & critical environments. Morgan is well-versed in both engineering and operations aspects, including high availability design, system integration, and lifecycle management. He also has a solid foundation in open-source and proprietary technologies - ranging from Apache, OpenLDAP or Kerberos to enterprise-grade systems like WebLogic. Morgan Patou holds an Engineering Degree in Computer Science from ENSISA (\u00c9cole Nationale Sup\u00e9rieure d'Ing\u00e9nieurs Sud Alsace) in Mulhouse, France. He is Alfresco Content Services Certified Administrator (ACSCA), Alfresco Content Services Certified Engineer (ACSCE) as well as OpenText Documentum Certified Administrator. His industry experience spans the Public Sector, IT Services, Financial Services\/Banking, and the Pharmaceutical industry.\",\"sameAs\":[\"https:\/\/blog.dbi-services.com\/author\/morgan-patou\/\",\"https:\/\/x.com\/MorganPatou\"],\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/morgan-patou\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Alfresco - Documents are searchable only after 3min - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/alfresco-documents-are-searchable-only-after-3min\/","og_locale":"en_US","og_type":"article","og_title":"Alfresco - Documents are searchable only after 3min","og_description":"I had a case at a customer recently where newly uploaded documents into Alfresco would always be searchable but only after 2min45s to 3min. The environment in question is an Alfresco Content Services 7.1 with High Availability (Repository and Share Clustering, Solr Sharding on multi-nodes, …) used for QA\/TEST. It’s an ongoing project to upgrade […]","og_url":"https:\/\/www.dbi-services.com\/blog\/alfresco-documents-are-searchable-only-after-3min\/","og_site_name":"dbi Blog","article_published_time":"2022-01-05T18:20:04+00:00","article_modified_time":"2022-04-06T06:26:26+00:00","author":"Morgan Patou","twitter_card":"summary_large_image","twitter_creator":"@MorganPatou","twitter_misc":{"Written by":"Morgan Patou","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/alfresco-documents-are-searchable-only-after-3min\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/alfresco-documents-are-searchable-only-after-3min\/"},"author":{"name":"Morgan Patou","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"headline":"Alfresco – Documents are searchable only after 3min","datePublished":"2022-01-05T18:20:04+00:00","dateModified":"2022-04-06T06:26:26+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/alfresco-documents-are-searchable-only-after-3min\/"},"wordCount":498,"commentCount":0,"keywords":["Alfresco","index","NTP","slowness"],"articleSection":["Application integration & Middleware","Enterprise content management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/alfresco-documents-are-searchable-only-after-3min\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/alfresco-documents-are-searchable-only-after-3min\/","url":"https:\/\/www.dbi-services.com\/blog\/alfresco-documents-are-searchable-only-after-3min\/","name":"Alfresco - Documents are searchable only after 3min - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2022-01-05T18:20:04+00:00","dateModified":"2022-04-06T06:26:26+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/alfresco-documents-are-searchable-only-after-3min\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/alfresco-documents-are-searchable-only-after-3min\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/alfresco-documents-are-searchable-only-after-3min\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Alfresco – Documents are searchable only after 3min"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8","name":"Morgan Patou","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g","caption":"Morgan Patou"},"description":"Morgan Patou has over 12 years of experience in Enterprise Content Management (ECM) systems, with a strong focus in recent years on platforms such as Alfresco, Documentum, and M-Files. He specializes in the architecture, setup, customization, and maintenance of ECM infrastructures in complex & critical environments. Morgan is well-versed in both engineering and operations aspects, including high availability design, system integration, and lifecycle management. He also has a solid foundation in open-source and proprietary technologies - ranging from Apache, OpenLDAP or Kerberos to enterprise-grade systems like WebLogic. Morgan Patou holds an Engineering Degree in Computer Science from ENSISA (\u00c9cole Nationale Sup\u00e9rieure d'Ing\u00e9nieurs Sud Alsace) in Mulhouse, France. He is Alfresco Content Services Certified Administrator (ACSCA), Alfresco Content Services Certified Engineer (ACSCE) as well as OpenText Documentum Certified Administrator. His industry experience spans the Public Sector, IT Services, Financial Services\/Banking, and the Pharmaceutical industry.","sameAs":["https:\/\/blog.dbi-services.com\/author\/morgan-patou\/","https:\/\/x.com\/MorganPatou"],"url":"https:\/\/www.dbi-services.com\/blog\/author\/morgan-patou\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/494","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/20"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=494"}],"version-history":[{"count":2,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/494\/revisions"}],"predecessor-version":[{"id":652,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/494\/revisions\/652"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=494"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=494"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=494"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=494"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}