Bug 1021822
| Summary: | Improve performance of ENCRYPT protocol | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Data Grid 6 | Reporter: | Martin Gencur <mgencur> |
| Component: | JGroups | Assignee: | Tristan Tarrant <ttarrant> |
| Status: | CLOSED NOTABUG | QA Contact: | Martin Gencur <mgencur> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.2.0 | CC: | bban, pslavice, rmarwaha, sjacobs |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-03-25 12:25:45 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Martin Gencur
2013-10-22 07:31:51 UTC
Bela Ban <bela> made a comment on jira JGRP-1722 See if ENCRYPT could be moved *down* the stack, e.g. just below the reliable retransmission protocols ({{NAKACK}, {{UNICAST}}). I seem to recall though that ENCRYPT has a dep on GMS. Bela Ban <bela> made a comment on jira JGRP-1722 See if ENCRYPT could be moved *down* the stack, e.g. just below the reliable retransmission protocols (NAKACK, UNICAST). I seem to recall though that ENCRYPT has a dep on GMS. Martin Gencur <mgencur> made a comment on jira JGRP-1722 The replication works also with ENCRYPT placed under NAKACK while AUTH is placed under GMS. My functional test for the ISPN server passes with this configuration. Data is successfully replicated. Bela Ban <bela> made a comment on jira JGRP-1722 I think this is only true if (a) there is no communication between joiner and coordinator needed or (b) the transport is reliable. * (a) If we have a shared keystore or username/password encryption, then this works * (b) If we need to send a key request to the coord, and the coord sends a response, then either the transport needs to be reliable or UNICAST needs to be below ENCRYPT, or else these requests are sent *unreliably* and might get lost. A possible solution for (b) could be to assume that the message sending is unreliable and send the key request to the coordinator until a valid key is received. In this case, ENCRYPT could be moved under NAKACK/UNICAST. [~mgencur] Either you used TCP as transport, or you were just lucky that the message wasn't dropped. Under real stress, there are no guarantees that a message isn't dropped. Bela Ban <bela> updated the status of jira JGRP-1722 to Resolved This needs further analysis. Moving target to 6.5. This will be revisited after 6.4 |