feat: Redis 설정에 비밀번호/TLS/타임아웃 지원 추가#197
Conversation
기존엔 로컬 Redis(비밀번호 없음, 평문 연결)만 전제로 했는데, Upstash 같은 관리형 Redis는 비밀번호 인증 + TLS가 필수라 연결 자체가 불가능했음. - spring.data.redis.password/ssl.enabled 프로퍼티로 조건부 활성화 (미설정 시 기존 로컬 docker-compose Redis와 100% 하위 호환) - Lettuce 연결/커맨드 타임아웃을 30초로 상향 (Render Free 티어는 0.1 CPU라 TLS 핸드셰이크 자체가 느려서, 기본 타임아웃 안에 핸드셰이크가 못 끝나고 "Connection closed prematurely"로 실패하는 문제 확인)
|
Warning Review limit reached
Next review available in: 50 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughRedis connectivity now uses configurable Lettuce client settings, including socket and command timeouts, optional password authentication, and optional SSL/TLS. ChangesRedis connection configuration
Estimated code review effort: 2 (Simple) | ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/main/java/org/runnect/server/config/redis/RedisConfig.java`:
- Around line 41-52: Update the SSL-enabled branch in RedisConfig’s
clientConfigBuilder setup to configure Lettuce SslOptions with a 30-second
handshakeTimeout before applying SSL. Keep SocketOptions.connectTimeout for TCP
connections and preserve the existing non-SSL configuration.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 7e134471-1609-4513-b598-4bb7d42d0f49
📒 Files selected for processing (1)
src/main/java/org/runnect/server/config/redis/RedisConfig.java
SocketOptions.connectTimeout은 TCP 연결 단계만 커버하고, TLS 핸드셰이크는 별도의 SslOptions.handshakeTimeout이 관리함. SSL 활성화 시에만 handshakeTimeout(30s)을 추가로 설정.
작업 배경
변경 사항
RedisConfig.java영향 범위
Connection closed prematurely로 실패 — 실측 확인 (로컬 JDK 11로는 즉시 성공, Render에서만 반복 실패)Test Plan
🤖 Generated with Claude Code
Summary by CodeRabbit