Full text search function is currently down. It sounds like something happened overnight. A client searched for "Fair and equitable treatment" yesterday (it was working fine producing the expected result), but it is not working today with 0 result.
A global search of "Fair and equitable treatment" shows that full text search isn't working.
We investigated above issue and found that this was because of indexing was not done correctly last night. We run the indexing again and it works fine now.
As we can see in 18th April's report shared by Paul, the indexing was not done correctly. In such cases we require to run the indexing again to generate correct index files.
We will monitor the indexing reports every day so that we can avoid such issues.
Notified 5 people
Paul Moon
Hi Anil:
Why is indexing done incorrectly? I see it is working fine now, but is there a way of alerting us when DT Search stops indexing instead of waiting until we get the daily report?
Thanks,
Paul
Notified 5 people
Anil Vaghela
Hello
Paul
,
We have checked on the server and everything looks good. We are assuming that there may be some issue with DTSearch indexing application.
In above scenario DTSearch didn't stop but it generated incorrect index files. In such scenario we can identify the issue only after indexing done. Hence we could only able to know about this issue once we have daily report.
We have done following change to identify such issue within an optimal time:
DTSearch indexing starts at 1.00 AM and completes at around 1.30 AM. We get daily report at around 2.00 AM which we have changed to 1.45 AM, so if we will check daily reports, we could able to identify such issue within 15 minutes and could take appropriate action.
Please let us know your thoughts.
Notified 5 people
Morgan Maguire,CEO
Hi
Anil
,
Sounds like a good approach going forward. Let's ensure that the reports are checked by you or someone else on the team as soon as they come in, and then you can take appropriate action if a discrepancy arises. Assuming this is done, we should minimize the window to 30 minutes or so between the indexing failure and the fix.
Thanks,
Morgan
Notified 5 people
Paul Moon
Thanks for the update, Anil. I echo Morgan's comment above.
Full text search function is currently down. It sounds like something happened overnight. A client searched for "Fair and equitable treatment" yesterday (it was working fine producing the expected result), but it is not working today with 0 result.
A global search of "Fair and equitable treatment" shows that full text search isn't working.
A specific full text search of "fair and equitable treatment" isn't producing any result either.
https://www.investorstatelawguide.com/ResearchTools/DTSearchFTS?action=search&newchkvalue=&toc=content&id=97&q=fair+and+equitable+treatment&testfeild=test&c1t=Free+Trade+Agreements%2CInternational+Treaties+%26+Rules%2CNAFTA%2COther%2CRegional%2FSectoral+Agreements%2C&agreementID=1234&provisionSourceID=&languageId=test&addselection=&tempno=12&countryid=&nodeid=&selNodeId=&country_id=&treaty_id=&rules_id=&fuzziness_id=1&language_id=A&disputid=&provision_idsource=&TreatiesandOtherInstrumentsid=&RulesofArbitrationid=&DispId=c2%2Cc3%2Cc4%2Cc5%2Cc6%2Cc7%2Cc8%2Cc9%2Cc10%2Cc11%2Cc12%2Cc13%2Cc14%2Cc15%2Cc16%2Cc17%2Cc18%2Cc19%2Cc20%2Cc22%2Cc23%2Cc24%2Cc25%2Cc26%2Cc28%2Cc29%2Cc30%2Cc31%2Cc32%2Cc33&drpdwnId=%2CSelect+Agreement&listId=test&c1t_name=&traty_instrument_id=&checkboxesCheckedValuePass=cat%3D3%5Etype%3D1%2C2%2C3%2C4%2C5%2C6%2C7%2C8%2C9%2C10%2C11%2C12%2C13%2C14%2C15%2C16%2C17%2C18%2C19%2C20%2C21%2C22%2C23%5E%5Ecat%3D3%5Etype%3D17%5E%5Ecat%3D3%5Etype%3D8%5E%5Ecat%3D3%5Etype%3D13%5E%5Ecat%3D3%5Etype%3D12%5E%5Ecat%3D3%5Etype%3D23%5E%5Ecat%3D3%5Etype%3D3%5E%5Ecat%3D3%5Etype%3D5%5E%5Ecat%3D3%5Etype%3D4%5E%5Ecat%3D3%5Etype%3D22%5E%5Ecat%3D3%5Etype%3D11%5E%5Ecat%3D3%5Etype%3D15%5E%5Ecat%3D3%5Etype%3D7%5E%5Ecat%3D3%5Etype%3D1%5E%5Ecat%3D3%5Etype%3D2%5E%5Ecat%3D3%5Etype%3D18%5E%5Ecat%3D3%5Etype%3D6%5E%5Ecat%3D3%5Etype%3D16%5E%5Ecat%3D3%5Etype%3D21%5E%5Ecat%3D3%5Etype%3D10%5E%5Ecat%3D1%5E%5ERulesArbitHidden%3DICSID+%28ICS%29%7CICSID+Additional+Facility%7CLondon+Courts+of+International+Arbitration%7CStockholm+Chamber+of+Commerce%7CUNCITRAL%5E%5Ecat%3D2%5E%5EInvestTreatyHidden%3DBilateral+Investment%7CFree+Trade+Agreement%7CInternational+Treaties+%24%24+Rules%7CNAFTA%7COther%7CRegional%2FSectoral&InvestmentTreaty_CountryId=&InvestmentTreaty_TreatyId=&All_circDate1=01%2F01%2F1899&All_circDate2=4%2F18%2F2018&RulesArbitHidden=&All_filter_country_id=&All_agreement_id=&All_Arbitrator=&All_ArbitratorRules=&searchType=boolean&ftypo=1&fuzziness=1&language=A&circDate1=01%2F01%2F1899&circDate2=4%2F18%2F2018&c1=1&c1_param=cat%3D3%5Etype%3D1%2C2%2C3%2C4%2C5%2C6%2C7%2C8%2C9%2C10%2C11%2C12%2C13%2C14%2C15%2C16%2C17%2C18%2C19%2C20%2C21%2C22%2C23&c2=1&c2_param=cat%3D3%5Etype%3D17&c3=1&c3_param=cat%3D3%5Etype%3D8&c4=1&c4_param=cat%3D3%5Etype%3D13&c5=1&c5_param=cat%3D3%5Etype%3D12&c6=1&c6_param=cat%3D3%5Etype%3D23&c7=1&c7_param=cat%3D3%5Etype%3D3&c8=1&c8_param=cat%3D3%5Etype%3D5&c9=1&c9_param=cat%3D3%5Etype%3D4&c10=1&c10_param=cat%3D3%5Etype%3D22&c11=1&c11_param=cat%3D3%5Etype%3D11&c12=1&c12_param=cat%3D3%5Etype%3D15&c13=1&c13_param=cat%3D3%5Etype%3D7&c14=1&c14_param=cat%3D3%5Etype%3D1&c15=1&c15_param=cat%3D3%5Etype%3D2&c16=1&c16_param=cat%3D3%5Etype%3D18&c17=1&c17_param=cat%3D3%5Etype%3D6&c18=1&c18_param=cat%3D3%5Etype%3D16&c19=1&c19_param=cat%3D3%5Etype%3D21&c20=1&c20_param=cat%3D3%5Etype%3D10&c21=1&c21_param=cat%3D1%5E%5ERulesArbitHidden%3DICSID+%28ICS%29%7CICSID+Additional+Facility%7CLondon+Courts+of+International+Arbitration%7CStockholm+Chamber+of+Commerce%7CUNCITRAL&c22=1&c22_param=cat%3D1%5E%5ERulesArbitHidden%3DICSID+%28ICS%29&c23=1&c23_param=cat%3D1%5E%5ERulesArbitHidden%3DICSID+Additional+Facility&c24=1&c24_param=cat%3D1%5E%5ERulesArbitHidden%3DLondon+Courts+of+International+Arbitration&c25=1&c25_param=cat%3D1%5E%5ERulesArbitHidden%3DStockholm+Chamber+of+Commerce&c26=1&c26_param=cat%3D1%5E%5ERulesArbitHidden%3DUNCITRAL&c27=1&c27_param=cat%3D2%5E%5EInvestTreatyHidden%3DBilateral+Investment%7CFree+Trade+Agreement%7CInternational+Treaties+%24%24+Rules%7CNAFTA%7COther%7CRegional%2FSectoral&c28=1&c28_param=cat%3D2%5E%5EInvestTreatyHidden%3DBilateral+Investment&c29=1&c29_param=cat%3D2%5E%5EInvestTreatyHidden%3DFree+Trade+Agreement&c30=1&c30_param=cat%3D2%5E%5EInvestTreatyHidden%3DInternational+Treaties+%24%24+Rules&c31=1&c31_param=cat%3D2%5E%5EInvestTreatyHidden%3DNAFTA&c32=1&c32_param=cat%3D2%5E%5EInvestTreatyHidden%3DOther&c33=1&c33_param=cat%3D2%5E%5EInvestTreatyHidden%3DRegional%2FSectoral&agreementIDprov=&agreementSeq=1#b
Thanks,
Paul
Also, there is still the outstanding issue of why this wasn't picked up the dtSearch reports.
Morgan
Just to give you an idea how DT Search daily result is different between yesterday and today
Yesterday (April 17th)
Today (April 18th)
We investigated above issue and found that this was because of indexing was not done correctly last night. We run the indexing again and it works fine now.
As we can see in 18th April's report shared by Paul, the indexing was not done correctly. In such cases we require to run the indexing again to generate correct index files.
We will monitor the indexing reports every day so that we can avoid such issues.
Why is indexing done incorrectly? I see it is working fine now, but is there a way of alerting us when DT Search stops indexing instead of waiting until we get the daily report?
Thanks,
Paul
We have checked on the server and everything looks good. We are assuming that there may be some issue with DTSearch indexing application.
In above scenario DTSearch didn't stop but it generated incorrect index files. In such scenario we can identify the issue only after indexing done. Hence we could only able to know about this issue once we have daily report.
We have done following change to identify such issue within an optimal time:
DTSearch indexing starts at 1.00 AM and completes at around 1.30 AM. We get daily report at around 2.00 AM which we have changed to 1.45 AM, so if we will check daily reports, we could able to identify such issue within 15 minutes and could take appropriate action.
Please let us know your thoughts.
Sounds like a good approach going forward. Let's ensure that the reports are checked by you or someone else on the team as soon as they come in, and then you can take appropriate action if a discrepancy arises. Assuming this is done, we should minimize the window to 30 minutes or so between the indexing failure and the fix.
Thanks,
Morgan
Paul