Skip to end of banner
Go to start of banner

Infrastructure Issues

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »


This page tracks infrastructure issues and time resolving them

Issue DescriptionEnvironment (carrier or FOLIO)Troubleshoot DateTime spent (hours)NotesResolved?By
Enabling profiler on mod-data-export, mod-source-record-storage - building mod-data-export and mod-source-record-storage from old scriptsFOLIO8/7, 8/113Seeing strange errors for mod-source-record-storage. Had to research, ask around. mod-data-export's profiler was enabled but the tasks did not stabilize, even after hours of waiting and a few times shut them all down and restarting themYesMartin
Data Export App crashing with Reactjs(white screen)FOLIO8/71Troubleshoot mod-data-export draining connections caused by enabling/disabling profiler YesVarun, Martin
Rebuilding Okapi to enable profiler results in Hazelcast errorsFOLIO8/1232 hours for fcp1, 1 hour for fcp1.  Hongwei pointed out what to do and it quickly fixed the issues.  (Could have taken 15-30 mins if had Hongwei's knowledge.YesMartin
Created a new branch of FSE configurations to feed in the custom docker entrypoint file to enable profiler on mod-data-export and mod-source-record-storage. FOLIO8/112Used the workaround Wayne provided, still does not workNoMartin
InfluxDB and Telegraf data on gcp1 nodes not shipping to carrier-io boxFOLIO8/7, 8/101Closely looked at the differences of subnets in gcp1 and fcp1 (where there is no such issue). Hongwei added a rule to the carrier-io security group to enable data to flow from gcp1 to fcp1YesMartin
Profiler on mod-data-export and mod-source-record-storage not profiling anything other than CPUandMemoryFOLIO? carrier-io8/122Looked at the logs of modules where enabling worked, compared them against these two modules' logs. Found a pattern. Follow up with carrier-io team is needed to understand more on how the profiler works. NoMartin, Roman
Upgrade gcp1 to latest q22020 releaseFOLIO8/102Backend modules were failing to register to okapi. Restarting all modules in ECS and retrying fixed the issue.YesVarun
  • No labels