[grpc-io]  Important Update: gRPCConf 2024 CFP Deadline Extended!

['Terry Wilson' via grpc.io]

Dear gRPC Community,

We're thrilled to announce that the Call for Proposals (CFP) deadline for 
gRPConf 2024 has been extended to May 29th, 2024!

We've heard your feedback and want to give everyone more time to submit 
their talks. Whether you're a seasoned gRPC expert or a newcomer to the 
community, we encourage you to share your knowledge and experiences with us.

This is your chance to be part of the premier gRPC event of the year and 
connect with fellow gRPC enthusiasts from the community.

Submit your proposal today and help us make gRPConf 2024 the best one yet!

To submit your proposal or register for the event,, please visit 
events.linuxfoundation.org/grpconf/program/cfp/.

We can't wait to see what you come up with!

Sincerely,

The gRPConf Team

events.linuxfoundation.org/grpconf/ 

Follow us on Youtube @gRPCio 


-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/f82d35d5-a318-4f21-9f4e-faa483eff39dn%40googlegroups.com.

[grpc-io] Re: Inquiry on Monitoring Deserialization Time of Protobuf Requests in gRPC

['Terry Wilson' via grpc.io]

This was also asked in https://github.com/grpc/grpc-java/issues/11217 and 
I've provided a reply there.

On Sunday, May 12, 2024 at 5:32:51 AM UTC-7 YACHEN ZHANG wrote:

> Dear Team,
>
> I am currently utilizing gRPC for our project and I have a specific 
> requirement that I need assistance with.
>
> I am interested in *measuring the time it takes to deserialize Protobuf 
> requests on the server side*. Could you please inform me if there is any 
> built-in monitoring capability in gRPC for this purpose? Alternatively, 
> could you advise which function I might use to log the time taken for this 
> process?
>
> Thank you in advance for your support and guidance.
>
> Best regards
>

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/707ae263-06a2-4075-a922-9d32a6bda450n%40googlegroups.com.

[grpc-io] gRPC-Java v1.64.0 Released

['Terry Wilson' via grpc.io]

The v1.64.0 release  
of gRPC-Java is now available!


API Changes
   
   - compiler: the option jakarta_omit was renamed @generated=omit (#11086 
   ) (8a21afc 
   

   )

New Features
   
   - New API LoadBalancer.getChannelTarget() (4561bb5 
   

   )
   - opentelemetry: Publish new module grpc-opentelemetry (5ba1a55 
   
).
 
   The feature is still missing documentation and an example. It only supports 
   metrics; tracing and logs will be future enhancements. See gRFC A66 
   
   - bazel: Add support for bzlmod (#11046 
   ) (d1890c0 
   

   )
   - bazel: Replace usages of the old compatibility maven targets with 
   @maven targets (0064991 
   

   )
   - okhttp: Support serverBuilder.maxConcurrentCallsPerConnection (Fixes 
   #11062 ). (#11063 
   ) (8050723 
   

   )
   - xds: Experimental metrics recording in WRR LB (06df25b 
   

   , 35a171b 
   

   , 2897b39 
   
),
 
   to be exported by grpc-opentelemetry if explicitly enabled in 
   GrpcOpenTelemetry. See gRFC A78 
   
   - rls: Experimental metrics recording in RLS LB (a9fb272 
   

   , a1d1932 
   

   , 8133318 
   
),
 
   to be exported by grpc-opentelemetry if explicitly enabled in 
   GrpcOpenTelemetry

Improvements
   
   - examples: support bazel build for retry policy example (58de563 
   

   )
   - netty: Allow deframer errors to close stream with a status code, as 
   long as headers have not yet been sent (e036b1b 
   
).
 
   This will greatly improve the debuggability of certain server errors in 
   particular cases. Instead of the client seeing “CANCELLED: RST_STREAM 
   closed stream. HTTP/2 error code: CANCEL”, they could see 
   “RESOURCE_EXHAUSTED: gRPC message exceeds maximum size 4194304: 6144592”
   - netty: Improve handling of unexpected write queue promise failures (
   #11016 )
   - servlet: Avoid unnecessary FINEST hex string conversion by checking 
   log level. Fixes #11031 . 
   (f7ee5f3 
   

   )
   - StatusException/StatusRuntimeException hide stack trace in a simpler 
   way (#11064 ) (e36f099 
   

   )
   - util: Status desc for outlier detection ejection (#11036 
   ) (10cb4a3 
   

   )
   - binder: Helper class to allow in process servers to use peer uids in 
   test (#11014 ) (537dbe8 
   

   )
   - Add load() statements for the Bazel builtin top-level java symbols (
   #11105 ) (add8c37 
   

   )
   - Add StatusProto.toStatusException overload to accept Throwable (#11083 
   ) (5c9b492 
   

   )

Bug fixes
   
   - Fix retry race condition that can lead to double decrementing 
   inFlightSubStreams and so miss calling closed (#11026 
   

[grpc-io] Call for Speakers! 10 Days left to submit a gRPConf 2024 proposal

['Terry Wilson' via grpc.io]

Hello gRPC Community,


We still have slots available for speakers to join us at gRPConf 2024. If  
you have a gRPC story to tell, an innovative use case to share, or a 
burning question to answer, we invite you to submit a proposal by May 19th!

Submit a Proposal 

Why you should speak:

   - 
   
   Share your gRPC knowledge
   - 
   
   Become a recognized expert
   - 
   
   Connect with fellow gRPC users
   
We want to hear about:

   - 
   
   How you're using gRPC
   - 
   
   Tips and tricks you've learned
   - 
   
   New ideas for gRPC projects
   
Keep an eye on the official gRPC website and social media channels for 
updates. If you’re not interested in speaking, but still want to join us 
you can Register Now! 

We can't wait to see you at gRPConf 2024!

The gRPConf Team

events.linuxfoundation.org/grpconf/ 
Follow us on Youtube @gRPCio 


-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/4388e8e4-98f6-47c9-86b9-101ad580de06n%40googlegroups.com.

[grpc-io] Save the Date - gRPConf 2024!

['Terry Wilson' via grpc.io]

Hello gRPC Community,

Mark your calendars for the premier gRPC event of the year! gRPConf 2024 
will land on the Google Cloud Campus in Sunnyvale, California, on August 
27th, 2024.

Get ready to:

   - 
   
   Dive into the latest gRPC developments
   - 
   
   Network with fellow gRPC users and experts
   - 
   
   Learn best practices and innovative use cases
   
More details, including registration and a Call for Proposals, will be 
coming soon. For now, block off August 27th, 2024, and stay tuned for 
updates!

Best regards,

The gRPConf Team

Follow us on YouTube @gRPCio  


-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/795cf320-355d-47dd-862d-f7fd42ce9986n%40googlegroups.com.

[grpc-io] Re: Is hedgingPolicy supported in C++

['Terry Wilson' via grpc.io]

Sorry, I don't believe C++ has implemented hedging.

On Monday, January 22, 2024 at 6:29:21 AM UTC-8 Leonid Lazarev wrote:

> Hello,
>
> Does "hedgingPolicy" is suported for C++ grpc or not?
>
> I see description for hedging in proposal, https://
> github.innominds.com/grpc/proposal/blob/master/A6-client-retries.md, but 
> I do not see that the configuration parameters for hedgind are parsed in 
> the code. 
>
> I use grpc 1.54.2
>
> Best Regards Leonid Lazarev
>

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/2c66f4f6-d304-4cbb-a439-44bd780cb22an%40googlegroups.com.

Re: [grpc-io] gRPC client fallback from load-balancer to round robin DNS endpoint on LB outage

['Terry Wilson' via grpc.io]

Krishna,

I'll mention that we also have a short guide on custom LBs 
 that can help you with 
the fundamentals.

On Monday, November 6, 2023 at 3:53:01 PM UTC-8 Larry Safran wrote:

> Yes, you will need a custom NameResolver.  
> You could have your NameResolver do one of the following
> 1)  Extend DnsNameResolver (as is done by the internal GrpcNameResolver) 
> and override the doResolve method
> 2)  Directly extend NameResolver and have a field with a DnsNameResolver 
> created through the DnsNameResolverProvider (which should be gotten from 
> the registry).  
>
> There is already a load balancer that is switching between 2 child load 
> balancers.  It is experimental and can be specified as 
> "priority_experimental".  What it does is to use a specific attribute that 
> must be set by the NameResolver.  Even if you go with your own load 
> balancer, that would be the best way to differentiate which addresses 
> should be used for which child.  If you want to use it as an example, it is 
> https://github.com/grpc/grpc-java/blob/master/xds/src/main/java/io/grpc/xds/PriorityLoadBalancer.java
>
>
>
> On Mon, Nov 6, 2023 at 1:53 PM Krishna Sai Veera Reddy <
> krishnasaiv...@gmail.com> wrote:
>
>> Hey Larry,
>>
>> Thank you for your response! Are there any examples out in the wild on 
>> how to do this? Also the part that is confusing me is the name resolution. 
>> Do we have to add a custom name resolution policy as well so that we get 
>> both the LB and round robin IP addresses in `acceptResolvedAddresses 
>> `
>>  
>> method in the LB policy?
>>
>> On Friday, November 3, 2023 at 12:50:20 PM UTC-7 Larry Safran wrote:
>>
>>> This is a perfect scenario for a custom LB policy.  Since LB policies 
>>> form a tree, you could easily have your policy delegate to either a 
>>> PickFirst or RoundRobin policy depending on whether or not the LB is up.  
>>> Just have your policy define a ForwardingLoadbalanceHelper whose 
>>> updateBalancingState passes the picker from the oppropriate downstream 
>>> policy.
>>>
>>> On Fri, Nov 3, 2023 at 12:29 PM Krishna Sai Veera Reddy <
>>> krishnasaiv...@gmail.com> wrote:
>>>
 Hello All,

 I am working on a gRPC client that connects to a gRPC service fronted 
 by an LB but would like the client to automatically fallback to using 
 round-robin DNS to directly connect to the backend servers when the LB 
 goes 
 down. How do I go about this? Would I need to implement my own custom LB 
 policy? Any help is appreciated and thanks in advance!

 -- 
 You received this message because you are subscribed to the Google 
 Groups "grpc.io" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to grpc-io+u...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/grpc-io/df8f4a85-5020-4c68-bb94-cbea67d7c75an%40googlegroups.com
  
 
 .

>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "grpc.io" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to grpc-io+u...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/grpc-io/2e7b95aa-cd66-40f5-bf41-0484fa12892cn%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/51db24a6-3faa-4f9e-a979-54a0d5368921n%40googlegroups.com.

[grpc-io] gRPC-Java v1.59.0 Released

['Terry Wilson' via grpc.io]

You can now grab the v1.59.0 
 release.

PLANNED ABI BREAKAGE!

This breaks the ABI of the @ExperimentalApi classes listed below.
This does not impact source code (API); it only impacts code compiled with 
a different version of gRPC than it runs with (ABI).

Users that recompiled their code using grpc-java v1.36.0 
 (released on Feb 
23, 2021) and later, ARE NOT AFFECTED.
Users that compiled their source using grpc-java earlier than v1.36.0 may 
need to recompile when upgrading to grpc-java v1.59.0.

See details in #10406 .

*Affected classes*

Class io.grpc.internal.AbstractManagedChannelImplBuilder is deleted, and no 
longer in the class hierarchy of the channel builders:

io.grpc.netty.NettyChannelBuilder
io.grpc.okhttp.OkhttpChannelBuilder
io.grpc.cronet.CronetChannelBuilder
Class io.grpc.internal.AbstractServerImplBuilder is deleted, and no longer 
in the class hierarchy of the server builders:

io.grpc.netty.NettyServerBuilder
io.grpc.inprocess.InProcessServerBuilder

API Changes
core: AbstractManagedChannelImplBuilder and AbstractServerImplBuilder are 
removed (#10530 ). This is 
ABI-breaking, see the warning above. (#10406 
)
core: Removed .class file hack previously introduced in v1.36.0 
 to ease removal of 
internal ABIs. (#10406 )
api: Add ForwardingChannelBuilder2, an ABI-safe version of 
ForwardingChannelBuilder, which will be deprecated in the following 
release. (#10585 , #10406 
)
api: Add LoadBalancer.FixedResultPicker convenience class for load balancer 
implementations. It is a replacement for ErrorPicker and EMPTY_PICKER added 
in 1.58.0
testing: Stabilize TestMethodDescriptors (#10530 
)

Behavior Changes
core: de-expermentalize pick first config parsing (#10531 
)
netty: Respect -Dio.netty.allocator.type=unpooled when getting Netty 
Allocator instead of ignoring it (#10543 
)
netty: Use UNAVAILABLE for connections closed while writing. Previously 
this would result in UNKNOWN
binder: Enable indirect addressing using s. (#10550 
)

Improvements
core: only use reflection to resolve InternalCensusStatsAccessor once 
instead of once per channel
core: enhance error message in the case of DEADLINE_EXCEEDED to indicate 
name resolution delay.
netty: When creating a connection, use java.util.logging formatting instead 
of String.format to avoid work when not logged
netty: Touch ByteBuf when message framing has been decoded. If the buffer 
is leaked, this helps narrow down the source of reference counting bug
java_grpc_library.bzl: Disable Automatic Exec Groups inside grpc libraries (
#10514 ). This improves 
compatibility with future Bazel versions while retaining Bazel 5.x 
compatibility

Bug Fixes
netty: Avoid NettyAdaptiveCumulator incorrectly releasing its input ByteBuf 
twice when reading messages under certain error conditions (#10537 
)
xds: Add fix for xdstp replacement for percent-encoded authorities (#10571 
)

Documentation
API documentation (Javadoc) for Server and Channel builders now correctly 
displays inherited methods and the class hierarchy. (#10406 
)
examples: add an example for OAuth (#10560 
)

Dependencies
Upgrade Netty to 4.1.97.Final

Acknowledgements
John Cormie (@jdcormie)
Stephane Landelle (@slandelle)
@kotlaja

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/64bd646c-5167-4201-9118-b18a8d5bd50dn%40googlegroups.com.

[grpc-io] Re: StreamObservers in multi-thread Java application

['Terry Wilson' via grpc.io]

Yes, you should not have two threads calling onNext() on the same 
StreamObserver. If you do, you can get messages interleaved with each other 
and most likely just produce garbage. 

You need to make sure that your application acquires a lock before calling 
any of the methods on StreamObserver. Note that you CAN concurrently call 
the separate StreamObserver instances you have for incoming an outgoing 
messages. 

On Wednesday, September 6, 2023 at 9:41:25 PM UTC-7 Quyen Pham Ngoc wrote:

> I use grpc in Java multithread application. The documentation says: "Since 
> individual StreamObservers are not thread-safe, if multiple threads will be 
> writing to a StreamObserver concurrently, the application must synchronize 
> calls." 
>
> Is it true that with every onNext request of each StreamObservers I have 
> to be thread-safe? What do I do when using StreamObserver in a multi-thread 
> application environment? What happens if thread-safety is not guaranteed?
>
> Sincerely thank you for your help
>

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/8129bb36-f694-4002-a224-a468dde883c7n%40googlegroups.com.

[grpc-io] 1 Week Until gRPConf 2023 - Almost Sold Out!

['Terry Wilson' via grpc.io]

Hello gRPC Community!

We are one week away from gRPConf 2023 and tickets are close to selling 
out. If you haven’t had a chance to register yet, please do so soon. 
Tickets are still available for only $99.

We’re also excited to share that we have added a limited number of “Meet a 
Maintainer” Sessions. These sessions are a chance to do an 1on1 meeting 
with one of the maintainers of gRPC in place of watching one of the gRPConf 
talks. You can sign up by completing this form. 


All the details are below. We’re looking forward to seeing everyone on 
September 20th!

️Register Here 
 

️September 20, 2023

Google Cloud Campus - Sunnyvale, CA

⏰Doors open at 8:30AM

藺Meet a Maintainer 

View the Schedule 



Thank you,

Terry Wilson and the gRPC Team

gRPConf 2023 Sunnyvale, CA | Register Now 


-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/e3aea7ae-c6d1-4caf-8815-e82f3a0a5194n%40googlegroups.com.

[grpc-io] Last Call: gRPConf 2023 Early Bird Registration Ends Today 

['Terry Wilson' via grpc.io]

Hello gRPC Community!


Today is the last day to take advantage of $50 Early Bird Registration for 
gRPConf 2023. Sign up today and join us for a full day of gRPC talks and 
discussion. Below are all the details you need to know!


✅Register Here 


️September 20, 2023

Google Cloud Campus - Sunnyvale, CA

⏰Doors open at 8:30AM

View the Schedule 



We are only two weeks away from the event and pricing will increase to $99 
starting tomorrow.


Thank you,

Terry Wilson and the gRPC Team

gRPConf 2023 Sunnyvale, CA | Register Now 


-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/25540447-c3dd-4b6d-b4bc-db62aa86eb67n%40googlegroups.com.

[grpc-io] [Last Call] Come Speak at gRPConf 2023!

['Terry Wilson' via grpc.io]

Hello gRPC Community!


This is the last call to get your proposals in to speak at gRPConf 2023. 
The deadline is July 9th (this Sunday).


Submit your proposals and find more information and tips HERE 
!


Those not interested in speaking are invited to register now 
 for just $50. 


We hope to see you all there.


Thank you,

The gRPC team



-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/3f63a155-1c62-4b3d-bdbc-f27666073f63n%40googlegroups.com.

[grpc-io] 5 Days Left to Submit at Talk for gRPConf 2023

['Terry Wilson' via grpc.io]

Hello gRPC Community!


Time is running out to submit a proposal to speak at gRPConf 2023. The 
deadline is July 9th (this Sunday).


Submit your proposals and find more information HERE 
!

Spots are still available and topics might include:

   - 
   
   gRPC in-production
   - 
   
   User Stories + Case Studies
   - 
   
   Implementation
   - 
   
   Ecosystem + Tooling
   - 
   
   Codelabs
   
Those not interested in speaking can register now 
 for just $50. 


We hope to see you all there!


Thank you,

The gRPC team

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/8dd065f0-0ea0-4baf-ab2b-5ab922880344n%40googlegroups.com.

[grpc-io] gRPConf 2023 talk proposal submission deadline now July 9th

['Terry Wilson' via grpc.io]

Hi everyone, we have extended the deadline for submitting gRPConf 2023 
 talk proposals to *July 9th*. 
If you want to reach out to the gRPC community this is a great opportunity! 
You can submit your talk here 
.

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/15a1045a-4659-43d9-beb2-ba9c9cb7af23n%40googlegroups.com.

[grpc-io] Re: Please join us for gRPConf 2023!

['Terry Wilson' via grpc.io]

A quick follow-up on the pricing for the event:

*Early Bird*: $50 USD (through September 6)
*Standard*: $99 USD (September 7 - Event)

Hope to see you there!

On Monday, June 12, 2023 at 2:23:12 PM UTC-7 Terry Wilson wrote:

> gRPConf 2023 is happening!
>
> Join us on the Google Cloud Campus for a full day of talks, demos, case 
> studies, and code labs. Experts will discuss real-world implementations of 
> gRPC, best practices for developers, and deep dives into specific topics. 
> This is a must-attend event for anyone using gRPC in their applications 
> today, as well as those considering gRPC for their enterprise 
> microservices. 
>
> There will be ample time to meet project leads and key members of the gRPC 
> ecosystem, network with peers, and ask questions.
> Save the Date:When: September 20, 2023Where: Google Cloud Campus - 
> Sunnyvale, CAWhat: gRPConf 2023 *↗︎ * 
> 
> Call for Papers:CFP Open: June 8-July 2, 2023Interested in Speaking at 
> gRPConf 2023? Submit a Proposal *↗︎* 
> 
> CLICK HERE TO REGISTER NOW 
> We Want to Hear from You!Schedule a session at grpc.io/meetJoin the gRPC 
> mailing 
> list  YouTube @grpcio 
>  | Twitter @grpcio 
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/3f664925-ac40-4611-a187-0ccc8707375dn%40googlegroups.com.

[grpc-io] Please join us for gRPConf 2023!

['Terry Wilson' via grpc.io]

gRPConf 2023 is happening!

Join us on the Google Cloud Campus for a full day of talks, demos, case
studies, and code labs. Experts will discuss real-world implementations of
gRPC, best practices for developers, and deep dives into specific topics.
This is a must-attend event for anyone using gRPC in their applications
today, as well as those considering gRPC for their enterprise
microservices.

There will be ample time to meet project leads and key members of the gRPC
ecosystem, network with peers, and ask questions.
Save the Date:When: September 20, 2023Where: Google Cloud Campus -
Sunnyvale, CAWhat: gRPConf 2023 *↗︎ *

Call for Papers:CFP Open: June 8-July 2, 2023Interested in Speaking at
gRPConf 2023? Submit a Proposal *↗︎*

CLICK HERE TO REGISTER NOW 
We Want to Hear from You!Schedule a session at grpc.io/meetJoin the
gRPC mailing
list  YouTube @grpcio
 | Twitter @grpcio


-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CAMnUFuCeTqhmbK_TxEOj5mCzpavmx6F%3D68ae8nXdsceA0hGfVw%40mail.gmail.com.

[grpc-io] Re: Any suggestion on how to perform load testing of gRPC client & streaming service

['Terry Wilson' via grpc.io]

I'll also mention that there is a gRPC plugin for Gatling 
 and that K6 also supports gRPC 
.

On Wednesday, March 29, 2023 at 4:27:54 PM UTC-7 Terry Wilson wrote:

> I don't have any personal experience in this tool, but I've seen community 
> use of ghz.sh. Maybe start by looking at what it provides.
>
> On Sunday, March 19, 2023 at 12:15:24 PM UTC-7 Shailendra Omkar wrote:
>
>> Hi Team,
>>
>> I need to perform load testing of my application which uses gRPC client & 
>> streaming service.
>>
>> Can you please suggest on below
>>
>>1. Tools to use
>>2. Videos, Reference links
>>3. Sample example
>>
>> Appreciate your help on this.
>>
>> Thanks
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/abbfdd84-891a-44ac-ae0e-60bc20d9a333n%40googlegroups.com.

[grpc-io] Re: Any suggestion on how to perform load testing of gRPC client & streaming service

['Terry Wilson' via grpc.io]

I don't have any personal experience in this tool, but I've seen community 
use of ghz.sh. Maybe start by looking at what it provides.

On Sunday, March 19, 2023 at 12:15:24 PM UTC-7 Shailendra Omkar wrote:

> Hi Team,
>
> I need to perform load testing of my application which uses gRPC client & 
> streaming service.
>
> Can you please suggest on below
>
>1. Tools to use
>2. Videos, Reference links
>3. Sample example
>
> Appreciate your help on this.
>
> Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/2254151d-39cb-43d5-b4eb-f49166bba87cn%40googlegroups.com.

[grpc-io] gRPC-Java 1.54.0 Released

['Terry Wilson' via grpc.io]

The v1.54.0 release  
is now available.

*New Features*
- xds: Add weightedRoundRobin LB policy. The WRR policy allows picking the 
subchannel by weight based on the metrics feedback from the backend using 
ORCA API. See gRFC A58: Weighted Round Robin LB Policy. (#9873)
- census: Add per call latency metric which is latency across all attempts 
(#9906)

*Examples*
- Add examples for gcp observability (#9967)

*Bugfixes*
- rls:Fix throttling in route lookup where success and error metrics had 
been inverted ([b/262779100](https://b.corp.google.com/262779100)) (#9874)
- protobuf: update external javadoc link (#9890)
- core: fix outlier detection default ejection time (#9889)
- xds: deletion only to watchers of same control plane (#9896)
- compiler: add missing break in switch statement (#9901)
- api: Target scheme is now properly case insensitive (#9899). 
`NameResolverProvider`s, however, are expected to return the scheme used 
for registration in lower-case
- api: ForwardingServerCall now forwards getMethodDescriptor(). Previously 
only SimpleForwardingServerCall forwarded the method

*Behavior Changes*
- xds:Allow a cluster’s sum of weights to exceed the maximum signed integer 
up to a limit of max unsigned integer (#9864)
- grpclb: no SRV lookup for "metadata.google.internal."

*Improvements*
- xds, orca: Allow removing OobLoadReportListener from a subchannel in 
OrcaOobUil. (#9881)
- services: ORCA API change to allow recording QPS in MetricRecorder and 
CallMetricRecorder. (#9866)
- Move name resolution retry from managed channel to name resolver (take 
#2) (#9812)
- Rename AbstractXdsClient to ControlPlaneClient (#9934)
- all: fix build with errorprone 2.18 (#9886)
- build: allow Java 11+ to use modern error prone
- errorprone: enable UnnecessaryAnonymousClass (#9927)
- core: add logger to OutlierDetectionLoadBalancer (#9880)
- census: add trace annotation to report received message sizes (#9944)
- gcp-observability: emit latency and payload size metrics by default when 
monitoring is enabled (#9893)
- gcp-observability: add trace information like TraceId and SpanId in logs 
for log correlation when both logging and traces are enabled (#9963)
- gcp-observability: close() will take longer, to ensure metrics and traces 
are flushed (#9972)
- gcp-observability: update status code type in logs to Google RPC code 
instead of an integer (#9959)
- gcp-observability: retain default opencensus-task identifier even when 
custom labels are specified in the configuration (#9982)
- Build Improvements (#9855)
- Fixes MethodDescriptor java documentation (#9860)
- api: forward getSecurityLevel on PartialForwardingServerCall (#9912)
- Updating ServerInterceptors.java to support different marshallers for 
Request and Response messages. (#9877)

*API stabilizations*
- Stabilize method ServerBuilder.intercept which had previously been marked 
experimental. (#9894)
- api:stabilize offloadExecutor usage in ManagedChannelBuilder and 
NameResolver. (#9931)

*Dependencies*
- netty:Upgrade Netty from 4.1.79 to 4.1.87, tcnative from 2.0.54 to 2.0.56 
(#9784)
- gcp-observability: Transitive gRPC components now have the same gRPC 
version
- gcp-observability : Google cloud logging updated to 3.14.5

*Acknowledgements*
Benjamin Peterson
Sergey Matyukevich
Asaf Flescher
Benjamin Einaudi
Carl Mastrangelo
Ivan Bahdanau

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/bf88c58b-b132-40d4-8eff-40d9865414e8n%40googlegroups.com.

Re: [grpc-io] grpc vs rest benchmark

['Terry Wilson' via grpc.io]

In case you are not already aware of them, you might be interested in the 
benchmarks the gRPC team 
maintains: https://grpc.io/docs/guides/benchmarking/

You will find a link there to a dashboard 
 with performance history as 
well as to the repo  with the benchmark 
code.

On Thursday, February 16, 2023 at 6:02:10 AM UTC-8 shobhit agarwal wrote:

> Thanks for replying,
> I am using the code from below article: 
>
> https://www.techgeeknext.com/spring-boot/spring-boot-grpc-example#google_vignette
>
> It's spring boot application.
> Even for single request grpc is response time is 100 ms and REST is taking 
> 12 ms only.
>
>
>
>
>
> On Thursday, 16 February 2023 at 19:10:45 UTC+5:30 Gordan Krešić wrote:
>
>> On 16. 02. 2023. 14:38, Gordan Krešić wrote: 
>> > 
>> > I did similar test about a month ago, check the thread "gRPC 
>> performance (Java)": https://groups.google.com/g/grpc-io/c/4-bfxJDc7_s 
>> > 
>> > Over there you even have a link to a repo with sample projects I used 
>> to test. 
>>
>> Forgot to mention: check repo from the last post (
>> https://groups.google.com/g/grpc-io/c/4-bfxJDc7_s/m/y1qqIg5nCAAJ), not 
>> the first one. 
>>
>> -gkresic. 
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/b6a0fa3b-fc9b-4762-af68-4fb3f66a37e7n%40googlegroups.com.

[grpc-io] gRPC-Java 1.45.4 released

['Terry Wilson' via grpc.io]

The v1.45.4 release is now available.

*Bug Fixes*

   - core: Free unused MessageProducer in RetriableStream (#9853 
   )
   

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/96564ba3-0fc9-4ff8-a2ca-5cf8bb60b423n%40googlegroups.com.

[grpc-io] Re: Question about proto message - breaking change behavior

['Terry Wilson' via grpc.io]

I can't comment on the C# specifics, but when dealing with protobuf 
changes, one should never reuse the ordinal numbers of deleted fields. If 
you don't need a field anymore, you should *reserve* the field number. You 
can find some documentation on this over here 
.

A better approach here for your version 2 would be:

message A {
  reserved 2;
  string field1 = 1;
  map field3 = 3*;*
}

This will avoid problems with coding/decoding the message, which I suspect 
you are experiencing here.

Hope that helps,
Terry


On Thursday, October 13, 2022 at 11:07:12 AM UTC-7 sre.ag...@gmail.com 
wrote:

> Hi All,
>
> I recently observed some behavior w.r.t proto message - 
> marshalling/unmarshalling. Wanted to know if there is a better way to 
> determine the contract break specifically for code written in C#?
>
> Client (Version 1) and server (Version 1) were using different versions of 
> a message with some **breaking change**. My understanding **was** in case 
> of a contract break we will see some sort of exception but turns out the 
> field (*field3*) was just an empty object [*Not null*]. In our scenario 
> it is possible to have an empty object for that field, so checking null or 
> empty object won't help either.
>
> Is there a guideline to determine a contract break at run time? Or do we 
> need to somehow ensure in our code change review process or build process 
> that ordinals are not changed?
>
> *Version 1*
> Message A {
> string field1 = 1;
> uint64 filed2 = 2;
> map field3 = 3;
> }
>
> *Version 2*
> Message A {
> string field1 = 1;
> map field3 =* 2;*
> }
>
> Regards,
> Vivek 
>

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/e5faf6bd-0cc9-43cd-ad5a-c450b7a9f06bn%40googlegroups.com.

[grpc-io] Last chance to sign up for gRPConf 2022

['Terry Wilson' via grpc.io]

Hi folks, this is your last chance to sign up for next week's KubeCon 2022 
in Detroit and more specifically gRPConf 2022 happening on Monday 10/24! 
Come learn about the latest developments from several talks we have 
prepared for you and bring your questions to the gRPC team. We are also 
very eager to hear what features you would like to see on the gRPC roadmap.

See you next week!

Register here: https://events.linuxfoundation.org/grpc-conf/register/
Schedule: https://events.linuxfoundation.org/grpc-conf/program/schedule/

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/4e9d0735-7b9d-487d-8dee-756db698fbb8n%40googlegroups.com.

[grpc-io] gRPC-Java 1.43.3 Released

['Terry Wilson' via grpc.io]

The v1.43.3 release is now available.

*Bugfixes*
   
   - android: fix for app coming to foreground #8850 
   
   - xds: fix the validation code to accept new-style 
   CertificateProviderPluginInstance wherever used

*Dependencies*
   
   - Bump protobuf to 3.19.6

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/d685b506-6853-45ff-bd67-fc449e40b57cn%40googlegroups.com.

[grpc-io] gRPC-Java v1.42.3 Released

['Terry Wilson' via grpc.io]

The v1.42.3 release is now available

*Dependencies*
   
   - Bump protobuf to 3.19.6

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/27a15b89-5b6f-48bf-81f9-a6b7776261cbn%40googlegroups.com.

[grpc-io] gRPC-Java 1.49.2 Released

['Terry Wilson' via grpc.io]

The v1.49.2 release  
is now available.

*Dependencies*
   
   - Bump protobuf to 3.21.7

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/a76a5f16-0bd1-4130-8374-6466cfad9c9en%40googlegroups.com.

[grpc-io] gRPC-Java 1.48.2 Released

['Terry Wilson' via grpc.io]

The v1.48.2 release  
is now available.

*Bug Fixes*
   
   - xds: Fix a bug in ring-hash load balancing policy that, during 
   TRANSIENT_FAILURE state, it might cause unnecessary internal connection 
   requests on subchannels. (#9537 
   )
   - auth: Fix AppEngine failing while retrieving access token when 
   instantiating a blocking stub using AppEngineCredentials (#9524 
   )
   - xds: channel_id hash policy now uses a random per-channel id instead 
   of an incrementing one. The incrementing id was the same for every process 
   of a binary, which was not the intention (#9453 
   )
   - bazel: Use valid target name for services and xds when overriding 
   Maven targets (#9422 ). 
   This fixes an error of the form no such target 
   '@io_grpc_grpc_java//services:services' for services and missing ORCA 
   classes for xds. The wrong target names were introduced in 1.47.0

*Dependencies*
   
   - Bump protobuf to 3.21.7

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/90c4717a-7ece-4cf9-a914-f0dbe1046cccn%40googlegroups.com.

[grpc-io] gRPC Java v1.49.0 Release

['Terry Wilson' via grpc.io]

Release v1.49.0 is now available on Maven Central.

https://github.com/grpc/grpc-java/releases/tag/v1.49.0

*New Features*


   - okhttp: Add `OkHttpServerBuilder`. The server can be used directly, 
   but is not yet available via `ServerBuilder.forPort()` and 
   `Grpc.newServerBuilderForPort()`. It passes our tests, but has seen no 
   real-world use. It is also lacking connection management features
   - okhttp: Add support for byte-based private keys via 
   TlsChannelCredentials and TlsServerCredentials
   - core: New outlier detection load balancer
   - googleapis: google-c2p resolver is now stabilized

*Bug Fixes*


   - core: Fix retry causing memory leak for canceled RPCs. (#9360)
   - core: Use SyncContext for InProcess transport callbacks to avoid 
   deadlocks. This fixes the long-standing issue #3084 which prevented using 
   directExecutor() in some tests using streaming RPCs
   - core: Disable retries with in-process transport by default (#9361). 
   In-process does not compute message sizes so can retain excessive amounts 
   of memory
   - bazel: Use valid target name for services and xds when overriding 
   Maven targets (#9422). This fixes an error of the form `no such target 
   '@io_grpc_grpc_java//services:services'` for services and missing ORCA 
   classes for xds. The wrong target names were introduced in 1.47.0
   - xds: channel_id hash policy now uses a random per-channel id instead 
   of an incrementing one. The incrementing id was the same for every process 
   of a binary, which was not the intention (#9453)
   - core: Fix a bug that the server stream should not deliver halfClose() 
   when the call is immediately canceled. The bug causes a bad message 
   INTERNAL, desc: Half-closed without a request at server call. (#9362)
   - xds: Remove shaded orca proto dependency in ORCA api. The shading was 
   broken and couldn't really be used. (#9366)

*Behavior Changes*


   - gcp-observability: Interceptors are now injected in more situations, 
   including for non-Netty transports and when using transport-specific APIs 
   like NettyChannelBuilder. (#9309 #9312 #9424)
   - gcp-observability: custom tags now extended to metrics and traces 
   (#9402 #9407)
   - gcp-observability: excludes RPCs into Google Cloud Ops backend for 
   instrumentation (#9436)
   - xds: xdsNameResolver now matches channel overrideAuthority in 
   virtualHost matching (#9405)

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/983252f3-aaf6-4c73-ad9f-bf28aab990cdn%40googlegroups.com.

[grpc-io] gRFC A52: gRPC xDS Custom Load Balancer Configuration

['Terry Wilson' via grpc.io]

Hi folks, I have a PR out for a new gRFC 
at: https://github.com/grpc/proposal/pull/298

This one covers custom load balancer policy configurations in the control 
plane and their delivery to gRPC via xDS.

Feel free to leave any comments!
Terry

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/8287a977-2d13-42db-b706-d31729f6c6d0n%40googlegroups.com.

[grpc-io] gRPC Java v1.45.0 Released

['Terry Wilson' via grpc.io]

The release v1.45.0  
is now available.

Bug Fixes
   
   - rls: fix child lb leak when client channel is shutdown (#8750 
   )
   - rls: fix RLS lb policy name (#8867 
   )
   - testing: fix GrpcCleanupRule issue when retrying tests (#8918 
   )
   - xds: Fix XdsNameResolver blindly propagates control plane errors (#8953 
   ). This change forces the 
   use of UNAVAILABLE for any xDS communication failures, which otherwise 
   could greatly confuse an application
   - xds: fix validation code to accept new-style 
   CertificateProviderPluginInstance (#8892 
   )
   - xds: fix a concurrency issue in CSDS ClientStatus responses (#8795 
   )
   - xds: Squelch "Failed to resolve name" ADS reconnection error logs. 
   Workaround for #8886  (
   #8942 )
   - xds: Improve priority failover handling for IDLE subpolicies (#8926 
   ). This mainly improves 
   behavior with ring_hash
   - bom: Include grpc-binder
   - binder: Fix a ServiceConnection leak (#8861 
   )
   - binder: Increase fairness across streams when limited by flow control. 
   This can dramatically reduce latency when channel is being used for high 
   throughput (#8835 )
   - android: fix for app coming to foreground (#8855 
   )

Behavior Changes
   
   - Local-only transparent retry is (practically) unlimited now. 
   Previously it was at most once per RPC.
   - xds: implement least_request load balancing policy (#8739 
   )

Dependencies
   
   - Bump Error Prone Annotations to 2.10.0
   - Bump Guava to 31.0.1-android
   - Bump Google Auth Library to 1.4.0
   - Bump Auto Value to 1.9
   - netty: Include both x86 and Arm64 epoll as dependency for 
   grpc-netty-shaded
   - testing: remove opencensus dependency from grpc-testing (#8833 
   )

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/122fd092-a43a-4427-86a9-06a3e6835565n%40googlegroups.com.

[grpc-io] gRPC-Java 1.41.1 Released

['Terry Wilson' via grpc.io]

gRPC Java 1.41.1 is released and is available on Maven Central.
https://github.com/grpc/grpc-java/releases/tag/v1.41.1

*Bug Fixes*

   - grpclb: Fix “IllegalStateException: already in fallback” channel 
   panic, by not starting fallback timer if already in fallback (#8646). This 
   builds on the fix in 1.38.1. The bug was introduced in 1.38.0.

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/94ccce55-6e9c-4d84-a779-bd7979df31f9n%40googlegroups.com.

[grpc-io] gRPC-Java 1.40.2 Released

['Terry Wilson' via grpc.io]

gRPC Java 1.40.2 is released and is available on Maven Central.
https://github.com/grpc/grpc-java/releases/tag/v1.40.2

*Bug Fixes*

   - grpclb: Fix “IllegalStateException: already in fallback” channel 
   panic, by not starting fallback timer if already in fallback (#8646). This 
   builds on the fix in 1.38.1. The bug was introduced in 1.38.0.
   

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/653da1fb-63bd-4189-9d0d-3253b3209d63n%40googlegroups.com.