Schema Registry does not seem to run on port 8081 out of the box

1,290 views
Skip to first unread message

Binoy Thomas

unread,
May 18, 2017, 11:21:01 AM5/18/17
to Confluent Platform
1. Following the instructions on http://docs.confluent.io/current/schema-registry/docs/intro.html
2. Started the Schema Registry - ./bin/schema-registry-start ./etc/schema-registry/schema-registry.properties


Not able to connect. lsof -i:8081 | grep LISTEN returns nothing. Don't see anything in the console when starting up that indicated any failure.

Binoy Thomas

unread,
May 18, 2017, 11:24:06 AM5/18/17
to Confluent Platform
By the way I downloaded the tar.gz package for OSX

Ewen Cheslack-Postava

unread,
May 18, 2017, 6:29:38 PM5/18/17
to Confluent Platform
The configuration you are using does specify to listen on 8081: https://github.com/confluentinc/schema-registry/blob/master/config/schema-registry.properties#L15

Do you have the log from the schema registry? It might indicate what is going wrong (for example, if it can't connect to zookeeper for Kafka, it may not start serving HTTP requests).

-Ewen

--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.
To post to this group, send email to confluent-platform@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/6385b13d-349b-4faf-a98b-30653126589a%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Binoy Thomas

unread,
May 18, 2017, 6:46:23 PM5/18/17
to Confluent Platform
Below are the logs from the console when executing  - ./bin/schema-registry-start ./etc/schema-registry/schema-registry.properties - from the confluent-3.2.1 directory
[2017-05-18 17:41:44,918] INFO SchemaRegistryConfig values:
metric.reporters = []
kafkastore.sasl.kerberos.kinit.cmd = /usr/bin/kinit
response.mediatype.default = application/vnd.schemaregistry.v1+json
kafkastore.ssl.trustmanager.algorithm = PKIX
authentication.realm =
ssl.keystore.type = JKS
kafkastore.topic = _schemas
metrics.jmx.prefix = kafka.schema.registry
kafkastore.ssl.enabled.protocols = TLSv1.2,TLSv1.1,TLSv1
kafkastore.topic.replication.factor = 3
ssl.truststore.password =
host.name = 10.20.20.90
kafkastore.bootstrap.servers = []
schema.registry.zk.namespace = schema_registry
kafkastore.sasl.kerberos.ticket.renew.window.factor = 0.8
ssl.endpoint.identification.algorithm =
compression.enable = false
kafkastore.ssl.truststore.type = JKS
avro.compatibility.level = backward
kafkastore.ssl.protocol = TLS
kafkastore.ssl.provider =
kafkastore.ssl.truststore.location =
response.mediatype.preferred = [application/vnd.schemaregistry.v1+json, application/vnd.schemaregistry+json, application/json]
kafkastore.ssl.keystore.type = JKS
ssl.truststore.type = JKS
kafkastore.ssl.truststore.password =
access.control.allow.origin =
ssl.truststore.location =
ssl.keystore.password =
port = 8081
kafkastore.ssl.keystore.location =
master.eligibility = true
ssl.client.auth = false
kafkastore.ssl.keystore.password =
kafkastore.security.protocol = PLAINTEXT
ssl.trustmanager.algorithm =
authentication.method = NONE
request.logger.name = io.confluent.rest-utils.requests
ssl.key.password =
kafkastore.sasl.mechanism = GSSAPI
kafkastore.sasl.kerberos.ticket.renew.jitter = 0.05
kafkastore.ssl.key.password =
zookeeper.set.acl = false
authentication.roles = [*]
metrics.num.samples = 2
ssl.protocol = TLS
kafkastore.ssl.keymanager.algorithm = SunX509
kafkastore.connection.url = localhost:2181
debug = false
listeners = [http://0.0.0.0:8081]
ssl.provider =
ssl.enabled.protocols = []
ssl.keystore.location =
ssl.cipher.suites = []
kafkastore.ssl.endpoint.identification.algorithm =
kafkastore.ssl.cipher.suites =
access.control.allow.methods =
kafkastore.sasl.kerberos.min.time.before.relogin = 60000
ssl.keymanager.algorithm =
 (io.confluent.kafka.schemaregistry.rest.SchemaRegistryConfig:169)
[2017-05-18 17:41:45,607] INFO Initializing KafkaStore with broker endpoints: PLAINTEXT://10.20.20.90:9092 (io.confluent.kafka.schemaregistry.storage.KafkaStore:131)
[2017-05-18 17:41:45,623] WARN The replication factor of the schema topic _schemas is less than the desired one of 3. If this is a production environment, it's crucial to add more brokers and increase the replication factor of the topic. (io.confluent.kafka.schemaregistry.storage.KafkaStore:336)

On Thursday, May 18, 2017 at 5:29:38 PM UTC-5, Ewen Cheslack-Postava wrote:
The configuration you are using does specify to listen on 8081: https://github.com/confluentinc/schema-registry/blob/master/config/schema-registry.properties#L15

Do you have the log from the schema registry? It might indicate what is going wrong (for example, if it can't connect to zookeeper for Kafka, it may not start serving HTTP requests).

-Ewen
On Thu, May 18, 2017 at 8:24 AM, Binoy Thomas <binoy....@piecestech.com> wrote:
By the way I downloaded the tar.gz package for OSX

On Thursday, May 18, 2017 at 10:21:01 AM UTC-5, Binoy Thomas wrote:
1. Following the instructions on http://docs.confluent.io/current/schema-registry/docs/intro.html
2. Started the Schema Registry - ./bin/schema-registry-start ./etc/schema-registry/schema-registry.properties


Not able to connect. lsof -i:8081 | grep LISTEN returns nothing. Don't see anything in the console when starting up that indicated any failure.

--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.

Binoy Thomas

unread,
May 18, 2017, 6:53:40 PM5/18/17
to Confluent Platform
Below is the Zookeeper logs - it seems to indicate a successful zookeeper connection (at least from the timestamps between the 2 logs)

[2017-05-18 17:41:08,389] INFO tickTime set to 3000 (org.apache.zookeeper.server.ZooKeeperServer)
[2017-05-18 17:41:08,389] INFO minSessionTimeout set to -1 (org.apache.zookeeper.server.ZooKeeperServer)
[2017-05-18 17:41:08,389] INFO maxSessionTimeout set to -1 (org.apache.zookeeper.server.ZooKeeperServer)
[2017-05-18 17:41:08,404] INFO binding to port 0.0.0.0/0.0.0.0:2181 (org.apache.zookeeper.server.NIOServerCnxnFactory)
[2017-05-18 17:41:23,364] INFO Accepted socket connection from /127.0.0.1:56265 (org.apache.zookeeper.server.NIOServerCnxnFactory)
[2017-05-18 17:41:23,413] INFO Client attempting to establish new session at /127.0.0.1:56265 (org.apache.zookeeper.server.ZooKeeperServer)
[2017-05-18 17:41:23,414] INFO Creating new log file: log.32 (org.apache.zookeeper.server.persistence.FileTxnLog)
[2017-05-18 17:41:23,423] INFO Established session 0x15c1db8c9500000 with negotiated timeout 6000 for client /127.0.0.1:56265 (org.apache.zookeeper.server.ZooKeeperServer)
[2017-05-18 17:41:24,008] INFO Got user-level KeeperException when processing sessionid:0x15c1db8c9500000 type:delete cxid:0x2f zxid:0x35 txntype:-1 reqpath:n/a Error Path:/admin/preferred_replica_election Error:KeeperErrorCode = NoNode for /admin/preferred_replica_election (org.apache.zookeeper.server.PrepRequestProcessor)
[2017-05-18 17:41:24,061] INFO Got user-level KeeperException when processing sessionid:0x15c1db8c9500000 type:create cxid:0x3c zxid:0x36 txntype:-1 reqpath:n/a Error Path:/brokers Error:KeeperErrorCode = NodeExists for /brokers (org.apache.zookeeper.server.PrepRequestProcessor)
[2017-05-18 17:41:24,062] INFO Got user-level KeeperException when processing sessionid:0x15c1db8c9500000 type:create cxid:0x3d zxid:0x37 txntype:-1 reqpath:n/a Error Path:/brokers/ids Error:KeeperErrorCode = NodeExists for /brokers/ids (org.apache.zookeeper.server.PrepRequestProcessor)
[2017-05-18 17:41:45,388] INFO Accepted socket connection from /0:0:0:0:0:0:0:1:56271 (org.apache.zookeeper.server.NIOServerCnxnFactory)
[2017-05-18 17:41:45,393] INFO Client attempting to establish new session at /0:0:0:0:0:0:0:1:56271 (org.apache.zookeeper.server.ZooKeeperServer)
[2017-05-18 17:41:45,395] INFO Established session 0x15c1db8c9500001 with negotiated timeout 30000 for client /0:0:0:0:0:0:0:1:56271 (org.apache.zookeeper.server.ZooKeeperServer)

Ewen Cheslack-Postava

unread,
May 18, 2017, 6:55:55 PM5/18/17
to Confluent Platform
Does the output just end there for the schema registry? The last log line is part way through the startup and there should be additional log messages before any processing starts. It will log a message like this:

Server started, listening for requests...

when it has actually finished starting up. Can you validate with, e.g., console-consumer that you are able to connect to the URL it is using for Kafka, 10.20.20.90:9092?

-Ewen

To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsubscribe@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.

Binoy Thomas

unread,
May 18, 2017, 7:03:50 PM5/18/17
to Confluent Platform
Yes it does stop there. After a certain time it dies 

[2017-05-18 17:46:50,771] ERROR Server died unexpectedly:  (io.confluent.kafka.schemaregistry.rest.SchemaRegistryMain:51)
org.apache.kafka.common.errors.TimeoutException: Timeout expired while fetching topic metadata

I didn't understand what you meant in the last statement...
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages