since I'm new to the Solr server. I don't know how can I find the port number of Solr using CMD in windows?. if any knows please do help in finding thanks in advance.
Usually, Solr is running on the port 8983. However, it may happen, that you have Solr server which is running on some different port. In this case you could check status of Solr server by running command:
./bin/solr.cmd status
which would provide information like this, if you have something running:
Found 1 Solr nodes:
Solr process 9713 running on port 8983
Related
Solr version 8.5.1
My solr is not starting anymore. I use solr start command to start the Solr. Every time I run this command I see the following error
Java HotSpot(TM) 64-Bit Server VM warning: JVM cannot use large page memory because it does not have enough privilege to lock pages in memory.
Waiting up to 30 to see Solr running on port 8983
ERROR: Solr at http://localhost:8983/solr did not come online within 30 seconds!
There is no error in the log files. But connecting to Solr is failing. This was working earlier.
Could someone please help me to troubleshoot the issue?
I found out what the issue is. Even though the message indicated that the server did not start in 30 seconds, it started after some time.
I closed the console window as the server was running in the background and it killed the server. The server is up as long as I keep the command window that I used to start the server.
given a zookeeper server ip:port, how to get the zookeeper structure?
for example I was told a zookeper service server is 192.1.2.17:2181
I can use ZKcli.sh to login and do some basic stuff. I can use it without problem.
But I want to know how many nodes in this zookeeper setup? Who are those nodes？? what are their status?
How do I achieve this?
Thanks
You might find some of these commands useful:
http://zookeeper.apache.org/doc/trunk/zookeeperAdmin.html#The+Four+Letter+Words
You can run them against the server ip:port you were given, e.g.:
echo MNTR | nc 192.1.2.17 2181
If you have access to that host, you could just check the configuration that is usually under something like <zoo install>/conf/zoo.cfg.
I am getting error failed to connect to 127.0.0.1:7199: connection refused when I do a nodetool status on my RHEL machine. It was working fine until yesterday but today it suddenly started giving this error. I did not make any changes to the configuration files.
I have DSE installed and properly configured as it was running fine till yesterday from past 3-4 months. The cassandra.yaml has the cluster name, seed, rpc address, rpc port, listen address all configured correctly. Also I set -Djava.rmi.server.hostname=<server ip address>; in cassandra-env.sh. Still did not work. Nor am I able to connect to cqlsh, nor my SOLR is accessible after this. Also I have allowed all ports on my security group on my machine to check if it is any port problem but it is not.
Any help would be appreciated.
Check your /etc/cassandra/cassandra.yaml file. It should be like
authenticator: AllowAllAuthenticator
Problem may be caused of this.
I was getting the same error, and it worked for me after the following commands:
systemctl start cassandra
systemctl restart cassandra
I read the documentation which says 7199 is JMX port number and 8983 is solr port number and 9160 is cassandra client port number. But if i start
dse cassandra -s
starts solr. If i start cassandra-client in the same machine
dse cassandra -f
It says
Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 7199; nested exception is:
java.net.BindException: Address already in use
So I understand that both tries to use same JMX port number.
Is there any way to specify two port numbers one for solr or one for cassandra OR is there any way to start both in the same machine.
I am using datastax 2.2.2 tarball set up.
Any ideas?
You only need to start dse one time. It runs search and c* in the same jvm and serves in all the ports you mentioned above.
As you mention above. Use this command for a tarball install to start dse in search mode. Do this accross your cluster (rolling restart, no downtime required):
bin/dse cassandra -s
Environment: Solr 1.4 on Windows/MS SQL Server
A write lock is getting created whenever I am trying to do a full-import of documents using DIH. Logs say "Creating a connection with the database....." and the process is not going forward (Not getting a database connection). So the indexes are not getting created. Note that no other process is accessing the index and even I restarted my MS SQL Server service. However still I see a write.lock file in my index directory.
What could be the reason for this? Even I have set the flag unlockOnStartup in solrconfig to be true, still the indexing is not happening.
Problem was resolved. There was some issue with the java update and the microsoft jdbc driver.