(I just did a google search for "solr", and all results on the first four pages referred to the engine, so I am curious.)
You can't judge by the first page of results anymore. Google is tweaking the results individually, as per your "programmer profile". Try doing a search on someone else computer.
I am somewhat biased because I am a - recent - Solr committer. But I also did try to do a very balanced comparison presentation two years ago: http://www.slideshare.net/arafalov/solr-vs-elasticsearch-cas... (kind of popular, 49k views...).
Solr - still - is more flexible than Elasticsearch by several degrees of magnitude. But Elasticsearch has a better vertical integration story, especially for analytics. And size (it IS small), because it does not ship OOTB with documentation (online), full examples (any?), Admin UI (plugin), rich-text extraction (plugin), data import mechanism (with rivers gone), etc.
If you don't need those, the choice is much more close. And many people do not need those. The problem is that most of the people don't know what they need and don't need when they do the evaluation, so they look at the most surface parameters.
Solr 6 has good startup scripts, (overly) comprehensive examples, REST APIs, well maintained 700 pages manual, etc. Some of these features are a bit harder to discover due to legacy information also being very visible. But it is there.
Elasticsearch has abandoned their search engine origins and embraced logging and analytics. Those that work in NLP and text processing are still using Solr. The edmismax parser is far more flexible and you can easily create your own query parser.
Elasticsearch excels at ease of use and supporting multiple programming languages via various clients. Solr is slowly moving away from XML, but cryptic query parser syntax remains.
Some colleagues went to an Elastic conference and felt there was foremost in a sales pitch than anything.