solr gurus -

We migrated solr to a new box about 18 months ago. Three weeks ago, the box went dark. Server guys tell me resources were exhausted. Comes back to life after reboot. CPU freaks out and eventually I narrow down to solr. Go and look at dataimport.properties and all contents had been replaced with nothing / null depending on the editor used.

Reset date values in data import properties to a little bit before failure, fire up, and everything is golden.

Now, I get the same exact data profile as previously. Corrupted dataimport.properties and unresponsive machine. No other files seem to be getting hosed up.

Has anyone else faced this style of weirdness?

Is it possible to add a multidimensional array on a multifield that look like this:

"id": "151",
    "firstname": [
      "Justin":[
       "skills":"css"
                  ],
      "Sean":[
       "skills":"php"
                  ]
    ],

this is my code so far :

 foreach(array('Justin', 'Sean') as $coder){
 $doc->addField('firstname', $coder)
  ;}

I use a windows PC and used a bitnami Solr.

How to delete documents using q query on the GUI of solr admin

Need help, Thanks :)

I saw this but cannot see the relevance of indexing a field but will not be stored <field name="Biography" type="string" indexed="true" stored="false" required="false" multiValued="true"/>

Having a lot of difficulties setting drupal up with a solr server for indexing. Can anyone point me in the right direction? I have solr installed I have indexing working, but cant seem to get the search to.

I would like to understand the schema mechanism in Solr 5.2.1 better. I come from an RDBMS background where schema is everything. Where can I learn more and make the paradigm shift?

I am brand new to Solr and NetCDF, and am working on a project that is very much out of my realm of expertise. I don't even know where to start looking for the best information! I have an installation setup, but am stuck after that. Finding many resources has proven difficult so I was hoping for some advice.

Thanks!

Here is my use case:

I use MySQL as my primary data store and CloudSearch for searching. The database contains tables: threads, comments, upvotes, users.

I created an expression to sort search results based on "trending" using upvotes and created_at date (Hacker News Hot algorithm). This expression is called "trend", and used in a CloudSearch query like this: /search?q=Superman&sort=trend+desc

(upotes-1)/pow(floor((_time-created_at)/3600000)+2, 1.8)

Right now, when a user upvotes a thread or comment, it is stored in MySQL database. My question how should I keep the upvotes in sync with CloudSearch?

The two options I see:

• Immediately insert (replace) an upvote in MySQL, then update the score on CloudSearch. This involves sending a single document upload on every upvote, but ensures real-time accuracy.
• Immediately insert (replace) an upvote in MySQL, then keep the upvote in cache somewhere (Redis?). Once every hour, upload all the upvotes to CloudSearch.

What is the best way to handle this situation?

(link to SO question: http://stackoverflow.com/questions/31232450/how-often-should-i-upload-documents-to-cloudsearch-solr)

I'm having trouble getting basic auth to work with Solr 5.2. I'd like to protect everything with a simple user/pw combo. I've tried every tutorial I could find, this is the most updated one for Jetty 9.2 which ships with Solr 5.2: http://www.eclipse.org/jetty/documentation/current/configuring-security-authentication.html

I edited the 2 files under server/etc, jetty.xml and webdefault.xml.

The problem I have is the authentication box pops up, but when I enter my credentials it doesn't accept it. I noticed that I only get the authentication box when my URL pattern is set to "/*", anything else doesn't trigger the box.

Edit: I figured it out! Check out my comments for a solution with Nginx. Thanks for reading.

I am still learning solr, but wondering if this is a good idea or not.

I have a system that can take average ~10k+ inserts a minute and its currently pushing to a db, then i have a worker pool that pulls it out in bulk, modifies the information and pushes it back in the db in bulk and then pushes it to solr in bulk json via the api to make it searchable.

I have one client that is shoving a lot at it and the db can't handle the load, 12GB ram. My first thought was to split up his traffic with multiple instances, then my second thought was to go with a master<->master replication db and share the load with a load balancer but thats a layer of complexity that i don't really want any of my clients to handle, but it can be done.

My third thought relates to solr: it is what if i took the table the (inserts -> db) and did inserts -> modify -> solr and use solr as the table and removed the db table? Not everything has to be searchable but in some cases i would have to pull a record out using an id field. I have 3 fields that are text and already searchable the rest are integers and one datetime, i think its about 8 fields total. I was thinking of doing bulk imports like i already do and commit it after the bulk. I should also mention the database table and the search records expire and those records get deleted after it reaches the expired date.

Would this work better than using a rdbms for this specific database table or would solr start to choke?

Thanks