-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy pathdevelopment-property-sharding.yaml
More file actions
123 lines (104 loc) · 3.21 KB
/
development-property-sharding.yaml
File metadata and controls
123 lines (104 loc) · 3.21 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
# Development Property Sharding Example
# This example is optimized for development and testing environments
#
# DEVELOPMENT NOTES:
# - Requires at least 2 servers (3+ recommended for HA)
# - Uses minimum viable resource allocation (4GB memory, 2 CPU cores)
# - Suitable for learning, testing, and small-scale development
# - NOT recommended for production workloads
# - Consider using regular Neo4j clusters for basic development
#
# ALTERNATIVE: For pure development without property sharding features,
# use examples/clusters/development-cluster.yaml instead
# Prerequisites: Create admin secret (REQUIRED)
# kubectl create secret generic neo4j-admin-secret \
# --from-literal=username=neo4j \
# --from-literal=password=dev-password
# Development property sharding cluster with minimal resources
apiVersion: neo4j.neo4j.com/v1alpha1
kind: Neo4jEnterpriseCluster
metadata:
name: dev-sharding-cluster
namespace: neo4j-dev
labels:
environment: development
purpose: testing
spec:
image:
repo: neo4j
tag: "2025.12.0-enterprise"
# Authentication required for property sharding
auth:
adminSecret: neo4j-admin-secret
# Minimum required servers for property sharding
topology:
servers: 3 # 3+ recommended for HA graph shard primaries
storage:
size: 2Gi # Small storage for dev
className: standard
# Development resources (minimum viable for property sharding)
resources:
requests:
memory: 4Gi # Absolute minimum for property sharding (8GB+ recommended for production)
cpu: 2000m # 2 cores for cross-shard queries
limits:
memory: 8Gi # Recommended for property sharding workloads
cpu: 2000m # Stable performance
# Enable property sharding with development-friendly settings
propertySharding:
enabled: true
config:
# Default required settings applied automatically
# Development-specific tuning
db.tx_log.rotation.retention_policy: "2 days" # Shorter retention
internal.dbms.sharded_property_database.property_pull_interval: "50ms" # Less aggressive
# Memory settings for development
server.memory.heap.max_size: "4G"
server.memory.pagecache.size: "1G"
# Enable more logging for development
dbms.logs.debug.level: "INFO"
---
# Simple sharded database for testing
apiVersion: neo4j.neo4j.com/v1alpha1
kind: Neo4jShardedDatabase
metadata:
name: test-sharded-db
namespace: neo4j-dev
labels:
purpose: testing
dataset: sample
spec:
clusterRef: dev-sharding-cluster
name: testdata
defaultCypherLanguage: "25"
propertySharding:
# Small number of shards for testing
propertyShards: 2
# Simple topology for development
graphShard:
primaries: 1 # Single primary for dev
secondaries: 1 # One backup
propertyShardTopology:
replicas: 1 # Single replica per shard
wait: true
ifNotExists: true
---
# Development namespace
apiVersion: v1
kind: Namespace
metadata:
name: neo4j-dev
labels:
purpose: development
environment: dev
---
# Simple admin credentials for development
apiVersion: v1
kind: Secret
metadata:
name: neo4j-admin-secret
namespace: neo4j-dev
type: Opaque
stringData:
username: "neo4j"
password: "development123"