It takes a little time for core discovery to enumerate all of the cores and fill in the various descriptors. That said, I'd be surprised if you actually can hit this very often since the coreDescriptor creation code also creates the cloudDescriptor and they're both loaded by the enumeration process and are just loaded from the core.properties file.
And the coreDescriptor isn't even added to the list of coreDescriptors until the cloudDescriptor has been built so I'd always expect getCoreDescriptor() to return null but _not_ getCOreDescriptor().getCloudDescriptor. So I'm really puzzled (or reading the code wrong). Erick On Wed, Apr 13, 2016 at 5:11 AM, Markus Jelsma <markus.jel...@openindex.io> wrote: > Hello - we use CloudDescriptor to get information about the collection. Very > early after starting Solr, we obain an instance: > cloudDescriptor = core.getCoreDescriptor().getCloudDescriptor(); > > In some strange cases, at some later point cloudDescriptor is null? Is it > possible cloudDescriptor is being set at some later stage in Solr? When > reading cloud information, do i always have to get a new cloudDescriptor > instance? > > Many thanks! > Markus
