Re: IllegalArgumentException: port out of range:-1 When Running Embedded Zookeeper Ensemble
Ok I have resolved it when I define host for -DzkRun parameter too. 2013/4/28 Furkan KAMACI > I am trying to run an embedded Zookeeper ensemble however I get that error: > > Apr 28, 2013 1:02:48 AM org.apache.solr.common.SolrException log > SEVERE: null:java.lang.IllegalArgumentException: port out of range:-1 > at java.net.InetSocketAddress.(InetSocketAddress.java:101) > at java.net.InetSocketAddress.(InetSocketAddress.java:81) > at > org.apache.solr.cloud.SolrZkServerProps.setClientPort(SolrZkServer.java:315) > > at > org.apache.solr.cloud.SolrZkServerProps.getMyServerId(SolrZkServer.java:278) > > at > org.apache.solr.cloud.SolrZkServerProps.parseProperties(SolrZkServer.java:453) > > at org.apache.solr.cloud.SolrZkServer.parseConfig(SolrZkServer.java:90) > at > org.apache.solr.core.CoreContainer.initZooKeeper(CoreContainer.java:228) > at org.apache.solr.core.CoreContainer.load(CoreContainer.java:520) > at org.apache.solr.core.CoreContainer.load(CoreContainer.java:405) > at > org.apache.solr.core.CoreContainer$Initializer.initialize(CoreContainer.java:337) > > at > org.apache.solr.servlet.SolrDispatchFilter.init(SolrDispatchFilter.java:110) > > at org.eclipse.jetty.servlet.FilterHolder.doStart(FilterHolder.java:119) > at > org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) > > at > org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:724) > > at > org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:265) > > at > org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250) > > at > org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:706) > > at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:492) > at > org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) > > at > org.eclipse.jetty.deploy.bindings.StandardStarter.processBinding(StandardStarter.java:39) > > at > org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:186) > at > org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(DeploymentManager.java:494) > > at > org.eclipse.jetty.deploy.DeploymentManager.addApp(DeploymentManager.java:141) > > at > org.eclipse.jetty.deploy.providers.ScanningAppProvider.fileAdded(ScanningAppProvider.java:145) > > at > org.eclipse.jetty.deploy.providers.ScanningAppProvider$1.fileAdded(ScanningAppProvider.java:56) > > at org.eclipse.jetty.util.Scanner.reportAddition(Scanner.java:609) > at org.eclipse.jetty.util.Scanner.reportDifferences(Scanner.java:540) > at org.eclipse.jetty.util.Scanner.scan(Scanner.java:403) > at org.eclipse.jetty.util.Scanner.doStart(Scanner.java:337) > at > org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) > > at > org.eclipse.jetty.deploy.providers.ScanningAppProvider.doStart(ScanningAppProvider.java:121) > > at > org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) > > at > org.eclipse.jetty.deploy.DeploymentManager.startAppProvider(DeploymentManager.java:555) > > at > org.eclipse.jetty.deploy.DeploymentManager.doStart(DeploymentManager.java:230) > > at > org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) > > at > org.eclipse.jetty.util.component.AggregateLifeCycle.doStart(AggregateLifeCycle.java:81) > > at > org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:58) > > at > org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:96) > > at org.eclipse.jetty.server.Server.doStart(Server.java:277) > at > org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) > > at > org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1266) > at java.security.AccessController.doPrivileged(Native Method) > at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1189) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.eclipse.jetty.start.Main.invokeMain(Main.java:472) > at org.eclipse.jetty.start.Main.start(Main.java:620) > at org.eclipse.jetty.start.Main.main(Main.java:95) > > I used that: > > -DzkRun -DnumShards=2 -Dbootstrap_confdir=./solr/collection1/conf > -Dcollection.configName=myconf -DzkHost=nem:9983,rem:9983,kem:9983 > > I read that thread: > http://lucene.472066.n3.nabble.com/solr4-0-problem-zkHost-with-multiple-hosts-throws-out-of-range-exception-td4014440.htmlI > use hostnames and when I ping I get respones to that hostnames. However > it doesn't work. I use Solr 4.2.1. > Any ideas? > > >
Re: Lucene native facets
https://issues.apache.org/jira/browse/SOLR-4774 On Fri, Apr 26, 2013 at 6:30 AM, Jack Krupansky wrote: > Sure, but they are completely different conceptual models of faceting - > Solr is dynamic, based on the actual data for the hierarchy, while Lucene > is static, based on a predefined taxonomy that must be meticulously created > before any data is added. > > Solr answers the question: what structure does your data have, while > Lucene answers the question how does your data fit into a predefined > structure. Both are valid and valuable questions, but they are still rather > distinct. > > Yes, Solr should provide support for static facet taxonomies, but what > exactly that would look like... has not even been proposed yet, yet alone > as simple as "facet.lucene=true". > > OTOH, maybe most of the work may be simply to add "taxonomy management" to > Solr (as a passthrough to the Lucene features), and then maybe a lot of the > existing Solr facet parameters simply need parallel Lucene-oriented > implementations. > > But, the other half of Solr facets is how filter queries are used for > selecting facets. That's all done at the application level, so it can't be > "hidden" from the app so easily. Maybe a new Solr facet filter API can be > developed that can then in turn have Solr facet vs. Lucene facet > implementations. Or, maybe a new dynamic facet Lucene API could be added as > well, so that Solr facets in fact become a passthrough as well. > > Still, it would be good to support Lucene facets in Solr. Maybe that could > be one of the key turning points for what defines Lucene/Solr 5.0. > > Is there a Jira for this? I don't recall one. > > -- Jack Krupansky > > -Original Message- From: William Bell > Sent: Friday, April 26, 2013 4:01 AM > To: solr-user@lucene.apache.org > Subject: Lucene native facets > > > Since facets are now included in Lucene, why don't we add a pass through > from Solr? The current facet code can live on but we could create new param > like facet.lucene=true? > > Seems like a great enhancement ! > > > -- > Bill Bell > billnb...@gmail.com > cell 720-256-8076 > -- Bill Bell billnb...@gmail.com cell 720-256-8076
