Deployments not making it to public ERDDAP

[kerfoot]

The following deployments have not made it to the public erddap end point:

http://54.91.88.156/users/rutgers/deployment/54870de6d24895413f2ae38d http://54.91.88.156/users/rutgers/deployment/5492e61cd248955ac2d6e2f4 http://54.91.88.156/users/rutgers/deployment/5492e75ad2489542cb8d3ecf

The NetCDF files have been uploaded, so the data sets should be there.

[kerfoot]

These 2 deployments are still not showing up as ERDDAP datasets:

http://54.91.88.156/users/rutgers/deployment/5492e61cd248955ac2d6e2f4 http://54.91.88.156/users/rutgers/deployment/5492e75ad2489542cb8d3ecf

[kerfoot]

@lukecampbell Are these deployments showing up on the private erddap? What's the url for the private erddap?

[lukecampbell]

Seeing these has led me down a hypothesis as to what is causing these hiccups. The first one has a lot of files that were all uploaded it looks like within one hour. I suspect that ERDDAP is trying to create the in-memory dataset or maybe an index of it, but it's unable to do so within the meager 30 seconds that the scripts expect.

[lukecampbell]

Well that wasn't it :\

[lukecampbell]

Ok, so these two new ones are all set.