I’d guess that #2 may be caused by #1 since PIO is unable to lookup metadata without ES or they are both caused by some resource being used up.
What template are you using? If ES is complaining I’d guess it’s the Universal Recommender? Is so, for some reason the connection to ES at query time is failing. What do you restart? Some resource may be getting used up like tmp disk storage that is erased on restart. You should think about what the restart affects. It clears the previous log files (unless to have them configured to rotate) it releases heap that might be configured to be too large for the machine, and maybe other things I haven’t thought of. How many machines are you using? What is the configuration? On Jan 4, 2017, at 1:30 AM, Harsh Mathur <harshmathur.1...@gmail.com> wrote: Hi, I am facing 2 issues which happen after a period of time and gets resolved after pio restart and pio redeploy. 1. While querying the pio for recommendations, it starts giving ES No Node available exception, But if we check ES health, its green. pio status also finds no fault in connecting to ES. 2. Invalid Access Key error keeps coming while pushing events in pio while using correct access key. Both these errors get resolved after restarting pio and redeploying the service. Any Suggestions? Regards Harsh Mathur harshmathur.1...@gmail.com <mailto:harshmathur.1...@gmail.com> “Perseverance is the hard work you do after you get tired of doing the hard work you already did."
