[CONTROLLER-1156] Clustering: Discarding oversized payload sent to Actor (RPC Gossip Messages) Created: 12/Feb/15 Updated: 19/Oct/17 Resolved: 13/Mar/15 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | mdsal |
| Affects Version/s: | Post-Helium |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Mark Mozolewski | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 2711 |
| Priority: | Normal |
| Description |
|
When running test specified in 2015-02-12 09:42:14,375 | ERROR | lt-dispatcher-19 | EndpointWriter | 195 - com.typesafe.akka.slf4j - 2.3.4 | Transient association error (association remains live) Moiz recommends matching the netty.tcp settings for the cluster-rpc actor system with the cluster-data actor system (akka.conf), i.e. add these missing fields: maximum-frame-size = 419430400 |
| Comments |
| Comment by Mark Mozolewski [ 12/Feb/15 ] |
|
Controller config file update: Matching Integration cluster deploy template file updates: |
| Comment by Tony Tkacik [ 12/Mar/15 ] |
|
I see commits merged, does change from WAITING_TO_REVIEW means that even after this patches issue is still there? Or should it be closed? |