FTS index creation on datetime field causes continuous FTS service restart (v5b)

Thanks – looks like a 8GB ram box.

The next question I’m wondering about (in my head) is how much memory was actually attempted to be memory mapped (mmap()'ed) during the error/failure.

The logged error msg doesn’t say, but I see there’s already been a recent fix to the error message that will report the actual mmap parameters in future builds… https://github.com/couchbase/moss/blame/master/store_footer.go#L303

In the meanwhile, I see from your index definition that you have some FTS features enabled that will use more storage…

      "store": true, // The index keeps a copy of the original field,
                     // used for search result highlighting/snippets.
      "include_term_vectors": true, // Allows for search highlighting
      "include_in_all": true // Allows for query string searches
                             // that don't need a field name, like searching for
                             // "2017" instead of "dob:2017"

and…

   "index_dynamic": true // Indexes all the fields

Turning those to false, if you don’t need them, will allow the index to be smaller, perhaps enough to allow mmap() to succeed.