Last Friday, Djinni, the largest Ukrainian IT job search platform, experienced a glitch that temporarily took down the site and resulted in the loss of 20,000 resumes. The company explained what happened.
Last Friday, Djinni, the largest Ukrainian IT job search platform, experienced a glitch that temporarily took down the site and resulted in the loss of 20,000 resumes. The company explained what happened.
The Djinni website outage began on June 27. The platform later resumed operations, but users were warned on social media about the possible loss of previously published resumes.
«Last Friday, we took down the site and „lost“ 22,000 resumes that were uploaded in June. If you are a candidate and have recently updated or uploaded your resume, check to see if it is there and upload it again if necessary», — Djinni commented on the failure.
The service also urged recruiters to notify candidates about the problem if they encounter a 404 error when opening a resume.
«On behalf of myself and the team, I want to apologize to our users, candidates, and recruiters. We were right. Mistakes happen, yes, but that’s no excuse. We could have prepared better, organized better, communicated better», — noted Maksym Ishchenko, founder of the DOU IT community and the Djinni platform.
The company explained that on Thursday, around midnight, they published a release that they had been working on for about a month and which was supposed to make working with resumes more convenient and secure for candidates.
«There were some problems during the deployment, but at 2 a.m. it looked like everything was up and running and the team went to bed. The problems started on Friday morning», — Ishchenko said.
According to him, the script removed 300,000 «outdated» files from the resume, but some of them were actually in use. The founder of the service explained that when the working day began, due to the peculiarities of the NFS volume, all requests with a 404 error acted as a DDOS of the site.
«We tried different options to get the resume database and our file storage back to working condition, but in the end we had to restore the backup from June 1… A terrible experience», — admitted Maksym Ishchenko.
He noted the irony of the situation, as the update was supposed to make working with resumes safer and more convenient, and called for support for the developers who worked on this release.
