Best Practices


  1. Version Selection Strategy

New Applications → Livy 3.5.5 ✅ Legacy Apps (3.3.x) → Livy 3.3.3 ⚠️ Compatibility Testing → Livy 3.5.1 🧪


  1. Port Standardization

Maintain consistent port allocation across environments:

Development: 8355, 8351, 8333 Staging: 8355, 8351, 8333 Production: 8355, 8351, 8333

  1. Client Configuration Management

Use environment-specific configuration files:

# config/livy_endpoints.py LIVY_ENDPOINTS = { 'production': { '3.5.5': 'http://livy-prod.company.com:8355', '3.3.3': 'http://livy-prod.company.com:8333', }, 'staging': { '3.5.5': 'http://livy-stg.company.com:8355', '3.3.3': 'http://livy-stg.company.com:8333', } }

  1. Graceful Deprecation

When deprecating older Livy versions:

  1. Announce deprecation (3-6 months' notice)

  2. Monitor usage (track active sessions)

  3. Migrate clients (provide migration guides)

  4. Disable new sessions (read-only mode)

  5. Decommission (after all clients migrated)


  Last updated on Jan 28, 2026
Next to read:
Livy 3 FAQs
null
On This Page
Best PracticesClient Configuration ManagementGraceful Deprecation