[GitHub] [pulsar] aahmed-se opened a new pull request #3992: Add exclusion for windows c++ compiler
aahmed-se opened a new pull request #3992: Add exclusion for windows c++ compiler URL: https://github.com/apache/pulsar/pull/3992 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [pulsar] aahmed-se commented on issue #3747: Closing FunctionAssignmentTailer should handle ConsumerAlreadyClosedException
aahmed-se commented on issue #3747: Closing FunctionAssignmentTailer should handle ConsumerAlreadyClosedException URL: https://github.com/apache/pulsar/pull/3747#issuecomment-480467102 run java8 tests This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [pulsar] ConcurrencyPractitioner commented on issue #3983: [Issue#3976] [component/client] Adding config for ReaderImpl
ConcurrencyPractitioner commented on issue #3983: [Issue#3976] [component/client] Adding config for ReaderImpl URL: https://github.com/apache/pulsar/pull/3983#issuecomment-480454749 @sijie I noticed that usually the user would either use startMessageId(long timestamp) or startMessageId(MessageId id) but not both. So should we make it so that we need to call only one of the methods to set the message id at which the user would need to start? Currently, it is required that MessageId id be a non-null parameter, so if the user wants to use startMessageId(long timestamp), they would also have to call startMessageId(MessageId id) with some dummy variable (id) as well. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [pulsar] rdhabalia commented on a change in pull request #3991: [pulsar-storm] Fix NPE while emitting next tuple
rdhabalia commented on a change in pull request #3991: [pulsar-storm] Fix NPE
while emitting next tuple
URL: https://github.com/apache/pulsar/pull/3991#discussion_r272766172
##
File path: pulsar-storm/src/main/java/org/apache/pulsar/storm/PulsarSpout.java
##
@@ -215,6 +204,36 @@ public void emitNextAvailableTuple() {
}
}
+private boolean emitFailedMessage() {
+Message msg;
+
+while ((msg = failedMessages.peek()) != null) {
+MessageRetries messageRetries =
pendingMessageRetries.get(msg.getMessageId());
+if (messageRetries != null) {
Review comment:
I wouldn't much worry about it because this piece of code is not being
reused and `nextTuple` anyway is calling `emitNextAvailableTuple` and I don't
think we want to do another method call for this small logic.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] [pulsar] rdhabalia commented on a change in pull request #3991: [pulsar-storm] Fix NPE while emitting next tuple
rdhabalia commented on a change in pull request #3991: [pulsar-storm] Fix NPE
while emitting next tuple
URL: https://github.com/apache/pulsar/pull/3991#discussion_r272766200
##
File path: pulsar-storm/src/main/java/org/apache/pulsar/storm/PulsarSpout.java
##
@@ -215,6 +204,36 @@ public void emitNextAvailableTuple() {
}
}
+private boolean emitFailedMessage() {
+Message msg;
+
+while ((msg = failedMessages.peek()) != null) {
+MessageRetries messageRetries =
pendingMessageRetries.get(msg.getMessageId());
+if (messageRetries != null) {
+// emit the tuple if retry doesn't need backoff else sleep
with backoff time and return without doing
+// anything
+if (Backoff.shouldBackoff(messageRetries.getTimeStamp(),
TimeUnit.NANOSECONDS,
+messageRetries.getNumRetries(),
clientConf.getDefaultBackoffIntervalNanos(),
+clientConf.getMaxBackoffIntervalNanos())) {
+
Utils.sleep(TimeUnit.NANOSECONDS.toMillis(clientConf.getDefaultBackoffIntervalNanos()));
+} else {
+// remove the message from the queue and emit to the
topology, only if it should not be backedoff
+LOG.info("[{}] Retrying failed message {}", spoutId,
msg.getMessageId());
+failedMessages.remove();
+mapToValueAndEmit(msg);
+}
+return true;
+}
+
+// messageRetries is null because messageRetries is already acked
and removed from pendingMessageRetries
+// then remove it from failed message queue as well.
+failedMessages.remove();
Review comment:
yes..let me add it.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] [pulsar] jai1 commented on a change in pull request #3991: [pulsar-storm] Fix NPE while emitting next tuple
jai1 commented on a change in pull request #3991: [pulsar-storm] Fix NPE while
emitting next tuple
URL: https://github.com/apache/pulsar/pull/3991#discussion_r272762647
##
File path: pulsar-storm/src/main/java/org/apache/pulsar/storm/PulsarSpout.java
##
@@ -215,6 +204,36 @@ public void emitNextAvailableTuple() {
}
}
+private boolean emitFailedMessage() {
+Message msg;
+
+while ((msg = failedMessages.peek()) != null) {
+MessageRetries messageRetries =
pendingMessageRetries.get(msg.getMessageId());
+if (messageRetries != null) {
Review comment:
Move this if statement to a separate function.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] [pulsar] jai1 commented on a change in pull request #3991: [pulsar-storm] Fix NPE while emitting next tuple
jai1 commented on a change in pull request #3991: [pulsar-storm] Fix NPE while
emitting next tuple
URL: https://github.com/apache/pulsar/pull/3991#discussion_r272763031
##
File path: pulsar-storm/src/main/java/org/apache/pulsar/storm/PulsarSpout.java
##
@@ -215,6 +204,36 @@ public void emitNextAvailableTuple() {
}
}
+private boolean emitFailedMessage() {
+Message msg;
+
+while ((msg = failedMessages.peek()) != null) {
+MessageRetries messageRetries =
pendingMessageRetries.get(msg.getMessageId());
+if (messageRetries != null) {
+// emit the tuple if retry doesn't need backoff else sleep
with backoff time and return without doing
+// anything
+if (Backoff.shouldBackoff(messageRetries.getTimeStamp(),
TimeUnit.NANOSECONDS,
+messageRetries.getNumRetries(),
clientConf.getDefaultBackoffIntervalNanos(),
+clientConf.getMaxBackoffIntervalNanos())) {
+
Utils.sleep(TimeUnit.NANOSECONDS.toMillis(clientConf.getDefaultBackoffIntervalNanos()));
+} else {
+// remove the message from the queue and emit to the
topology, only if it should not be backedoff
+LOG.info("[{}] Retrying failed message {}", spoutId,
msg.getMessageId());
+failedMessages.remove();
+mapToValueAndEmit(msg);
+}
+return true;
+}
+
+// messageRetries is null because messageRetries is already acked
and removed from pendingMessageRetries
+// then remove it from failed message queue as well.
+failedMessages.remove();
Review comment:
Add a debug log here, in case people complain that their messages are not
delivered or redelivered.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] [pulsar] rdhabalia opened a new pull request #3991: [pulsar-storm] Fix NPE while emitting next tuple
rdhabalia opened a new pull request #3991: [pulsar-storm] Fix NPE while
emitting next tuple
URL: https://github.com/apache/pulsar/pull/3991
### Motivation
[PulsarSpout] removes messages from
[pendingMessageRetries](https://github.com/apache/pulsar/blob/master/pulsar-storm/src/main/java/org/apache/pulsar/storm/PulsarSpout.java#L126)
but it doesn't remove from the `failedMessages` queue because of that
PulsarSpout throws NPE while [emitting next
tuple](https://github.com/apache/pulsar/blob/master/pulsar-storm/src/main/java/org/apache/pulsar/storm/PulsarSpout.java#L181)
stack-trace with old pulsar-storm lib: 1.20
2019-04-05 18:49:58.240 b.s.util CmsSpout_[1 1] [INFO] Async loop Stacktrace
is: {} java.lang.NullPointerException
at
org.apache.pulsar.storm.PulsarSpout.emitNextAvailableTuple(PulsarSpout.java:176)
at org.apache.pulsar.storm.PulsarSpout.nextTuple(PulsarSpout.java:160)
at
backtype.storm.daemon.executor$fn__7365$fn__7380$fn__7411.invoke(executor.clj:577)
at backtype.storm.util$async_loop$fn__551.invoke(util.clj:491)
at clojure.lang.AFn.run(AFn.java:22)
at java.lang.Thread.run(Thread.java:748)
```
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] [pulsar] grantwwu commented on issue #3602: Build docker images from directories instead of tgz files
grantwwu commented on issue #3602: Build docker images from directories instead of tgz files URL: https://github.com/apache/pulsar/pull/3602#issuecomment-480424971 run integration tests This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [pulsar] jerrypeng opened a new pull request #3990: improving getting version and git SHA
jerrypeng opened a new pull request #3990: improving getting version and git SHA URL: https://github.com/apache/pulsar/pull/3990 ### Motivation Improving the method in which we retrieve the version and git properties. ### Modifications Just use a template file and substitute properties for literals Get rid of properties files that is not necessary Move code to pulsar-common so other modules have access to the code as well This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [pulsar] lovelle edited a comment on issue #3988: [issue #3975] Bugfix NPE on non durable consumer
lovelle edited a comment on issue #3988: [issue #3975] Bugfix NPE on non durable consumer URL: https://github.com/apache/pulsar/pull/3988#issuecomment-480337745 Hi @ConcurrencyPractitioner please take a look at this pull, you might face this issue adding tests on #3983 to `Reader` with reset by timestamp This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [pulsar] lovelle commented on a change in pull request #3983: [Issue#3976] [component/client] Adding config for ReaderImpl
lovelle commented on a change in pull request #3983: [Issue#3976]
[component/client] Adding config for ReaderImpl
URL: https://github.com/apache/pulsar/pull/3983#discussion_r272734341
##
File path:
pulsar-client/src/main/java/org/apache/pulsar/client/impl/ReaderImpl.java
##
@@ -87,7 +91,13 @@ public void reachedEndOfTopic(Consumer consumer) {
consumer = new ConsumerImpl<>(client,
readerConfiguration.getTopicName(), consumerConfiguration, listenerExecutor,
partitionIdx, consumerFuture, SubscriptionMode.NonDurable,
readerConfiguration.getStartMessageId(), schema, null,
client.getConfiguration().getDefaultBackoffIntervalNanos(),
client.getConfiguration().getMaxBackoffIntervalNanos());
-
+try {
+if (readerConfiguration.getTimestamp().longValue() != -1) {
Review comment:
Explicit unwrapping is no longer necessary since Java 5
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] [pulsar] rdhabalia commented on issue #3986: [pulsar-broker] Introduce publish rate-limiting on topic
rdhabalia commented on issue #3986: [pulsar-broker] Introduce publish rate-limiting on topic URL: https://github.com/apache/pulsar/pull/3986#issuecomment-480384330 rerun java8 tests rerun integration tests This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [pulsar] merlimat commented on issue #3989: [Question] Geo Replication docs out of date?
merlimat commented on issue #3989: [Question] Geo Replication docs out of date? URL: https://github.com/apache/pulsar/issues/3989#issuecomment-480372057 @wmccarley Thanks for pointing out. the doc is indeed out of date. That was the behavior with Pulsar 1.x but we corrected the naming and simplified the namespaces in 2.0 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [pulsar] wmccarley opened a new issue #3989: [Question] Geo Replication docs out of date?
wmccarley opened a new issue #3989: [Question] Geo Replication docs out of date? URL: https://github.com/apache/pulsar/issues/3989 The documentation on [Geo Replication](https://pulsar.apache.org/docs/latest/admin/GeoReplication/#creating-global-namespaces) mentions: > Replication must be used with global topics, meaning topics that belong to a global namespace and are thus not tied to any particular cluster... **Global namespaces need to be created in the global virtual cluster.** Is this part of documentation still valid? It seems I can create namespaces that replicate between two clusters (i.e. creating a namespace for a given tenant and then using set-clusters to set both ) without having to use the virtual cluster notation mentioned on this page.. Replication seems to work fine. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [pulsar] rdhabalia removed a comment on issue #3986: [pulsar-broker] Introduce publish rate-limiting on topic
rdhabalia removed a comment on issue #3986: [pulsar-broker] Introduce publish rate-limiting on topic URL: https://github.com/apache/pulsar/pull/3986#issuecomment-480347575 retest this please This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [pulsar] rdhabalia commented on issue #3986: [pulsar-broker] Introduce publish rate-limiting on topic
rdhabalia commented on issue #3986: [pulsar-broker] Introduce publish rate-limiting on topic URL: https://github.com/apache/pulsar/pull/3986#issuecomment-480347575 retest this please This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [pulsar] merlimat commented on issue #3984: Fixed issue in backoff builder configuration
merlimat commented on issue #3984: Fixed issue in backoff builder configuration URL: https://github.com/apache/pulsar/pull/3984#issuecomment-480341594 run java8 tests run integration tests This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [pulsar] lovelle edited a comment on issue #3988: [issue #3975] Bugfix NPE on non durable consumer
lovelle edited a comment on issue #3988: [issue #3975] Bugfix NPE on non durable consumer URL: https://github.com/apache/pulsar/pull/3988#issuecomment-480337745 Hi @ConcurrencyPractitioner please take a look at this pull, you maybe face this issue adding tests on #3983 to `Reader` with reset by timestamp This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [pulsar] lovelle commented on issue #3988: [issue #3975] Bugfix NPE on non durable consumer
lovelle commented on issue #3988: [issue #3975] Bugfix NPE on non durable consumer URL: https://github.com/apache/pulsar/pull/3988#issuecomment-480337745 Hi @ConcurrencyPractitioner please take a look at this pull, you maybe face this issue adding tests on #3983 for `Reader` with reset by timestamp This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [pulsar] lovelle commented on a change in pull request #3988: [issue #3975] Bugfix NPE on non durable consumer
lovelle commented on a change in pull request #3988: [issue #3975] Bugfix NPE on non durable consumer URL: https://github.com/apache/pulsar/pull/3988#discussion_r272656686 ## File path: managed-ledger/src/main/java/org/apache/bookkeeper/mledger/ManagedLedger.java ## @@ -193,6 +193,7 @@ * @return the new NonDurableCursor */ ManagedCursor newNonDurableCursor(Position startCursorPosition) throws ManagedLedgerException; +ManagedCursor newNonDurableCursor(Position startPosition, String subscriptionName) throws ManagedLedgerException; Review comment: I think that the correct action here would be to modify existing `newNonDurableCursor` instead of adding a new one, but I did that way in order to leave this change as easy as possible, please let me know what you think. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [pulsar] lovelle opened a new pull request #3988: [issue #3975] Bugfix NPE on non durable consumer
lovelle opened a new pull request #3988: [issue #3975] Bugfix NPE on non durable consumer URL: https://github.com/apache/pulsar/pull/3988 **Motivation** Trying to fix #3975 When a reset of a cursor is performed with some timestamp on a non-durable consumer the message finder will fail with null pointer exception due to `cursor.getName()` being null. **Modifications** - Add method overloading for `newNonDurableCursor()` with subscription name. - Fix method getNonDurableSubscription to call `newNonDurableCursor()` with proper subscription name - Add test to assert issue. ### Verifying this change - [ ] Make sure that the change passes the CI checks. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [pulsar] chairmank opened a new issue #3987: 404 response to GET /admin/v2/tenants/{tenant} even though tenant exists
chairmank opened a new issue #3987: 404 response to GET
/admin/v2/tenants/{tenant} even though tenant exists
URL: https://github.com/apache/pulsar/issues/3987
**Describe the bug**
The admin REST API returns a 404 Not Found response to `GET
/admin/v2/tenants/$TENANT` even when `GET /admin/v2/tenants` shows that
`$TENANT` exists.
**To Reproduce**
Using Pulsar 2.3.0:
```
# Create tenant with an empty request body
$ curl -X PUT http://host/admin/v2/tenants/foo
# List tenants shows the newly created tenant
$ curl -X GET http://host/admin/v2/tenants
["foo","public"]
# Trying to get the newly created tenant returns 404 Not Found
$ curl -X GET http://host/admin/v2/tenants/foo
{"reason":"Tenant does not exist"}
```
After I update the tenant so that it has a valid `allowedClusters`, the get
request returns a 200 OK response:
```
$ curl -X POST -v -H 'Content-Type: application/json' -d
'{"adminRoles":[],"allowedClusters":["mycluster"]}'
http://host/admin/v2/tenants/foo
$ curl -X GET http://host/admin/v2/tenants/foo
{"adminRoles":[],"allowedClusters":["mycluster"]}
```
**Expected behavior**
I expect a 200 OK response with an empty response body, like
```
{"adminRoles":[],"allowedClusters":[]}
```
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] [pulsar] shan2015seyfert edited a comment on issue #3981: Error during handshake for tls auth by apache pulsar client on ubuntu server
shan2015seyfert edited a comment on issue #3981: Error during handshake for tls auth by apache pulsar client on ubuntu server URL: https://github.com/apache/pulsar/issues/3981#issuecomment-480179776 > @shan2015seyfert it seems you either connecting with TLS to a cleartext port (or the reverse) I can do telnet to port 8443, 6651 and this is enable `-Djava.net.preferIPv4Stack=true` in file `bin/pulsar-admin-common.sh`. What and where i need to do changes to allow working with `webServiceUrl=https://localhost:8443/ ` and `brokerServiceUrl=pulsar+ssl://localhost:6651/` Also i am using command `bin/pulsar standalone` to start the pulsar. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[pulsar] branch asf-site updated: Updated site at revision 0b92463
This is an automated email from the ASF dual-hosted git repository.
mmerli pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/pulsar.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 90cf796 Updated site at revision 0b92463
90cf796 is described below
commit 90cf7960802822437553528ef7d56438244d6a6a
Author: jenkins
AuthorDate: Fri Apr 5 09:00:31 2019 +
Updated site at revision 0b92463
---
content/swagger/swagger.json | 52 ++--
1 file changed, 26 insertions(+), 26 deletions(-)
diff --git a/content/swagger/swagger.json b/content/swagger/swagger.json
index 5315c68..914bc64 100644
--- a/content/swagger/swagger.json
+++ b/content/swagger/swagger.json
@@ -7096,9 +7096,24 @@
"type" : "number",
"format" : "double"
},
+"lastUpdate" : {
+ "type" : "integer",
+ "format" : "int64"
+},
+"msgThroughputIn" : {
+ "type" : "number",
+ "format" : "double"
+},
+"msgThroughputOut" : {
+ "type" : "number",
+ "format" : "double"
+},
"cpu" : {
"$ref" : "#/definitions/ResourceUsage"
},
+"directMemory" : {
+ "$ref" : "#/definitions/ResourceUsage"
+},
"bandwidthIn" : {
"$ref" : "#/definitions/ResourceUsage"
},
@@ -7108,29 +7123,14 @@
"memory" : {
"$ref" : "#/definitions/ResourceUsage"
},
-"underLoaded" : {
+"overLoaded" : {
"type" : "boolean"
},
-"overLoaded" : {
+"underLoaded" : {
"type" : "boolean"
},
"loadReportType" : {
"type" : "string"
-},
-"directMemory" : {
- "$ref" : "#/definitions/ResourceUsage"
-},
-"lastUpdate" : {
- "type" : "integer",
- "format" : "int64"
-},
-"msgThroughputIn" : {
- "type" : "number",
- "format" : "double"
-},
-"msgThroughputOut" : {
- "type" : "number",
- "format" : "double"
}
}
},
@@ -7290,15 +7290,15 @@
"type" : "number",
"format" : "double"
},
-"producerName" : {
- "type" : "string"
-},
"connectedSince" : {
"type" : "string"
},
"clientVersion" : {
"type" : "string"
},
+"producerName" : {
+ "type" : "string"
+},
"address" : {
"type" : "string"
}
@@ -8004,15 +8004,15 @@
"type" : "string"
}
},
-"producerName" : {
- "type" : "string"
-},
"connectedSince" : {
"type" : "string"
},
"clientVersion" : {
"type" : "string"
},
+"producerName" : {
+ "type" : "string"
+},
"address" : {
"type" : "string"
}
@@ -8112,11 +8112,11 @@
"ResourceUnit" : {
"type" : "object",
"properties" : {
-"availableResource" : {
- "$ref" : "#/definitions/ResourceDescription"
-},
"resourceId" : {
"type" : "string"
+},
+"availableResource" : {
+ "$ref" : "#/definitions/ResourceDescription"
}
}
},
[GitHub] [pulsar] shan2015seyfert commented on issue #3981: Error during handshake for tls auth by apache pulsar client on ubuntu server
shan2015seyfert commented on issue #3981: Error during handshake for tls auth by apache pulsar client on ubuntu server URL: https://github.com/apache/pulsar/issues/3981#issuecomment-480179776 > @shan2015seyfert it seems you either connecting with TLS to a cleartext port (or the reverse) I can do telnet to port 8443, 6651 and this is enable `-Djava.net.preferIPv4Stack=true` in file `bin/pulsar-admin-common.sh`. What and where i need to do changes to allow working with `webServiceUrl=https://localhost:8443/ ` and `brokerServiceUrl=pulsar+ssl://localhost:6651/` This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
