You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2020/09/28 08:08:43 UTC

[GitHub] [pulsar] Syphixs opened a new issue #8146: Producer Timeout if Schema exists

Syphixs opened a new issue #8146:
URL: https://github.com/apache/pulsar/issues/8146


   **Describe the bug**
   We use Kubernetes and require the new Oauth2 Authentification feature to work with our Services. So I started to build the new Image ( Commit: fecd8712e71202de5551897378c89b96e5d89219 ) and creating the container via the build script.
   The pulsar broker is sitting behind a Pulsar Proxy and all Services have a TLS Connection. Authentication is enabled on the Proxy as well as the Broker. Authorization just on the broker side with forward credentials settings on the Proxy. Now writing to a Topic without a Schema ( guess Byte Schema is the default ) works perfectly, but if a Topic has already a Schema ( In our case AVRO) it always gets a Timeout Error. The same thing happens if i communicate with the Broker directly ( so skipping the Proxy). Also tried to disable all Authentication and Authorization but the same problem occurs. Strangely with the standalone Pulsar Version and just putting a Proxy in front of it works. 
   
   **To Reproduce**
   Steps to reproduce the behavior:
   1. Build new Image 
   2. Build Container
   3. Deploy to Kubernetes with Oauth2 Settings
   4. Create Topic with Schema ( Strange thing is if you let it update Schema automatically. Say from bytes to AVRO it will do that. Even tells you afterwards the Schema is not correct if it is false but if it's valid it just gets the timeout. 
   5. Publish to that Topic with correct Schema.
   
   **Expected behavior**
   Publish to Topic if Schema is correct. 
   
   **Screenshots**
   Test Cluster:
   <img width="780" alt="Screenshot 2020-09-28 at 09 47 33" src="https://user-images.githubusercontent.com/33832024/94404664-a66b9c80-016f-11eb-9b9f-b40f17026940.png">
   
   Avro Schema on Topic: (auto generated with python Client) 
   <img width="686" alt="Screenshot 2020-09-28 at 09 49 10" src="https://user-images.githubusercontent.com/33832024/94404851-f21e4600-016f-11eb-9179-dec92dbbd4dc.png">
   
   Send test data with valid form: 
   <img width="2720" alt="Screenshot 2020-09-28 at 09 52 12" src="https://user-images.githubusercontent.com/33832024/94405585-0f9fdf80-0171-11eb-8a43-1e4a01c7116d.png">
   
   Proxy Log:
   <img width="1882" alt="Screenshot 2020-09-28 at 09 52 56" src="https://user-images.githubusercontent.com/33832024/94405872-73c2a380-0171-11eb-988d-8ae756c34d39.png">
   
   Broker Log:
   <img width="3347" alt="Screenshot 2020-09-28 at 10 04 28" src="https://user-images.githubusercontent.com/33832024/94406398-43c7d000-0172-11eb-8321-8ee78427ad05.png">
   
   
   
   **Desktop (please complete the following information):**
    - IOS
   - Debian 10
   
   


----------------------------------------------------------------
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:
users@infra.apache.org



[GitHub] [pulsar] Syphixs commented on issue #8146: Producer Timeout if Schema exists

Posted by GitBox <gi...@apache.org>.
Syphixs commented on issue #8146:
URL: https://github.com/apache/pulsar/issues/8146#issuecomment-700633835


   Also tried with java client. Seems to be the same issue.
   
   ![a41c75e1-cec5-46c3-bb55-0d60bea39c11](https://user-images.githubusercontent.com/33832024/94551218-4cdd9d80-0255-11eb-8822-05a54be6f4b0.jpg)
   


----------------------------------------------------------------
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:
users@infra.apache.org



[GitHub] [pulsar] Syphixs commented on issue #8146: Producer Timeout if Schema exists

Posted by GitBox <gi...@apache.org>.
Syphixs commented on issue #8146:
URL: https://github.com/apache/pulsar/issues/8146#issuecomment-700522476


   I did not try to produce with a java client yet. Thought the problem could not be from the client cause it's working with the standalone server perfectly. 
   
   Attached is the producer test code.
   [producer.zip](https://github.com/apache/pulsar/files/5297355/producer.zip)
   
   


----------------------------------------------------------------
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:
users@infra.apache.org



[GitHub] [pulsar] codelipenghui commented on issue #8146: Producer Timeout if Schema exists

Posted by GitBox <gi...@apache.org>.
codelipenghui commented on issue #8146:
URL: https://github.com/apache/pulsar/issues/8146#issuecomment-700372793


   Looks the problem is related to the python client, have you tried other client such as Java client? And could you please provide your producer code?


----------------------------------------------------------------
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:
users@infra.apache.org



[GitHub] [pulsar] danielorf commented on issue #8146: Producer Timeout if Schema exists

Posted by GitBox <gi...@apache.org>.
danielorf commented on issue #8146:
URL: https://github.com/apache/pulsar/issues/8146#issuecomment-781618668


   @Syphixs It's been a few months.  Have you managed to sort out the issue?  I'm planning to follow a very similar configuration.


----------------------------------------------------------------
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:
users@infra.apache.org