|
|
启动集群：3 ?" b* d) g/ I5 t/ L
) ^8 Z$ |5 ?3 H. O8 }9 _
前提：设置好系统配置和JVM堆内存) V( [0 R! I3 c: e+ t
7 a: V0 {$ \- a+ o, c8 B/ X
创建elastic的数据和日志存放目录，如果是测试环境无所谓，如果是生成环境一定要单独设置数据和日志存放的路径，因为ES可能因为升级或其它原因把原有的数据清理或丢失等因素
& e% H- a0 N7 V/ x6 |5 U; F- y
, }' P* p& j( G
4 G) g- f5 X, A8 r1 G+ Q f; R: V4 D% ?( D: j" Q3 s8 U
4 r: O* n* u$ `- _( p# @/ m% g% a
配置文件属组权限，并启动
$ S: j8 [6 K6 u9 {' d[root@it-elassearch elasticsearch]# chown -R es:es elastic-cluster1/
( a" I1 M: U( n[root@it-elassearch-2 elasticsearch]# chown -R es:es elastic-cluster2/7 ^7 M2 G% a( Q$ v
( V3 |9 o5 H0 D
! p: Y% ^3 Y( f2 J0 c) t
) e3 A! K+ p P
如果添加鉴权配置请按照此处配置，不配置即可略过：
3 c$ Y- c0 f9 {2 }6 i9 m5 R% h) ?" z/ d8 d$ L1 u+ m- S
- z5 k. ~7 r# N) ^& r6 I4 @( y
生成密匙：
' M" l6 ^( d C[es@it-elassearch elasticsearch-8.15.0]$ ./bin/elasticsearch-certutil ca
5 A, Y: ~- Q8 h$ z' @9 CThis tool assists you in the generation of X.509 certificates and certificate4 k$ n0 m. c3 J" q& B5 P3 T' K+ N
signing requests for use with SSL/TLS in the Elastic stack.
# Y; w' I2 d+ b
& i) t, R7 i- G+ Z0 @* I s, x) t6 V5 ?- v0 T' [) ~9 A
The 'ca' mode generates a new 'certificate authority') N- w# `* p" p0 O, S0 i
This will create a new X.509 certificate and private key that can be used
5 z. J: c. Z0 ?. T* Jto sign certificate when running in 'cert' mode.
, n/ [0 J/ M+ T; E8 e
& o8 a( H- w. S5 O+ {2 g4 o9 _5 ~
4 s% S; q' C- H: `Use the 'ca-dn' option if you wish to configure the 'distinguished name'
" a$ V. g% m% n+ s: o/ ~9 o7 sof the certificate authority
1 l3 T! g5 s* Z! J9 q- N* ]( E1 ~0 _8 Q3 p
: [, n6 d4 q9 w6 ]- Q
By default the 'ca' mode produces a single PKCS#12 output file which holds:$ T7 \) E! g) |% p5 `
* The CA certificate7 \+ d# z2 Y4 x
* The CA's private key
* E& A# \8 i6 ?
7 e* O7 I" l0 |9 ]) H" C9 E# \% z' `7 k$ a; X5 d+ e' Q
If you elect to generate PEM format certificates (the -pem option), then the output will
. `+ }2 x% e5 `" L; X: Y- tbe a zip file containing individual files for the CA certificate and private key
6 w# k9 g/ e% k; J. D+ B9 p; V
8 P. O3 M( R2 @5 o! c% t. W( ^8 APlease enter the desired output file [elastic-stack-ca.p12]: 【这里忽略，直接回车进入下面输入密码：】9 P o0 `/ I* B, l
Enter password for elastic-stack-ca.p12 : 【输入密码】6 f! l7 d8 H. f+ j
, ]; a' w) b* J* e7 \1 D4 B" J+ b( B7 |1 \
; Y [0 t0 H# R% e0 F7 B[es@it-elassearch elasticsearch-8.15.0]$ ll
$ H- j7 L. O$ c5 l* i4 Ktotal 2268
. m* q# p( f2 Q......
0 c' p& G! l- N( ]; [/ e5 p( X4 v-rw------- 1 es es 2672 Oct 28 17:05 elastic-stack-ca.p12" B' f/ X# Y1 O, Y9 J3 m3 l% t$ E
......% r7 j, F( S, O8 t: k3 \4 e
- @4 T: D I* F r. A1 F L+ H
2 Q3 t! b9 b& S+ [% D
. Z1 L& K- u6 a I8 e
+ p) @- \3 |' y4 z2 C9 S9 I! j- Y% X7 z, k$ `4 `
/ O; d1 e5 W2 ^# d1 q3 Z[es@it-elassearch-2 elasticsearch-8.15.0]$ ./bin/elasticsearch-certutil ca
- b7 b: h o; o, u+ `5 ?This tool assists you in the generation of X.509 certificates and certificate
# c' _9 c; ]) L1 tsigning requests for use with SSL/TLS in the Elastic stack.7 ~: J* G5 H8 z! i2 q
) W* x0 k- W( L+ e; l2 h
0 z" r1 M# b# J* }8 w' [The 'ca' mode generates a new 'certificate authority'3 Q+ m6 @* O0 z0 l. r% }+ @' D2 x
This will create a new X.509 certificate and private key that can be used
/ x: A9 a! @0 ^- v) O( C1 \) s+ N) p# Zto sign certificate when running in 'cert' mode.6 h* h6 a7 C( T9 ^+ c) b
+ |8 r+ f/ v! s/ Q4 S7 x7 b" o7 J4 a
' g$ Z: z1 d" m1 T
Use the 'ca-dn' option if you wish to configure the 'distinguished name'
- y+ L% t+ s! \0 p, Q6 N+ o( Oof the certificate authority6 T2 S) u. a1 e, F( u0 E
( Y0 l k* n4 \6 [5 N1 N1 Q5 M1 ~6 v. v# h# @/ o" X) v
By default the 'ca' mode produces a single PKCS#12 output file which holds:/ l9 {; X# ]% r/ h m, \% g
* The CA certificate
9 C. P) T" \* [ * The CA's private key
% {% q3 r! ^% @/ P% Z' d7 }) ]! L' W- ^+ _ M$ v
( \" e- B- W% H8 G- |If you elect to generate PEM format certificates (the -pem option), then the output will
7 j) S1 o) G( x1 hbe a zip file containing individual files for the CA certificate and private key
7 K9 y/ N5 { d% \# q+ t* M: B% u+ }+ }$ Z5 Z6 ?
a" J" a' y3 I1 t4 W V
Please enter the desired output file [elastic-stack-ca.p12]:
6 T1 _% x; ] `9 I/ K9 jEnter password for elastic-stack-ca.p12 :4 y5 f% c9 u! M1 q) L% L2 M! _$ b9 S
I7 L; u# `! Z9 P. u9 T( F! U+ `7 l, A( K
生成密钥：/ z9 @" ?9 S, k B
: Y' h( u6 o& x' L& A$ ?
- w8 a+ _. O8 ~[es@it-elassearch elasticsearch-8.15.0]$ ./bin/elasticsearch-certutil cert --ca elastic-stack-ca.p12 ! z) S) b3 G) y+ V
This tool assists you in the generation of X.509 certificates and certificate
3 D& v! V- s8 j5 P0 `) v+ Rsigning requests for use with SSL/TLS in the Elastic stack.; Q! U% z8 y1 _/ `
4 ?8 U; Y9 z% \3 M9 s. ^' SThe 'cert' mode generates X.509 certificate and private keys.
2 [; l; ~/ r3 f% c. {1 H * By default, this generates a single certificate and key for use8 q+ |: `5 t" k8 W& M
on a single instance.
7 h+ l) r f+ \$ f- p7 w# c * The '-multiple' option will prompt you to enter details for multiple
1 ~# ^" w* K# {! [6 i; Z instances and will generate a certificate and key for each one, U4 ^. @7 v/ k9 {& c* M0 u
* The '-in' option allows for the certificate generation to be automated by describing
" i0 l1 P( j4 D, v; c' T, w; x# @ the details of each instance in a YAML file% ], k# t& Z0 |% y$ }
4 q5 M" F( k# ?1 ?7 r8 Z6 K0 c* C: j/ D
* An instance is any piece of the Elastic Stack that requires an SSL certificate.
; W \6 z( v$ L/ E; r) { Depending on your configuration, Elasticsearch, Logstash, Kibana, and Beats
7 w5 U9 r. p! H1 [% R# ~ may all require a certificate and private key.7 v/ L; C+ X8 {: ], `
* The minimum required value for each instance is a name. This can simply be the; \; }' [ v/ M, I* C( }9 I
hostname, which will be used as the Common Name of the certificate. A full
) g/ }+ e* j+ c3 o distinguished name may also be used.1 i( T& O1 V9 M
* A filename value may be required for each instance. This is necessary when the
0 R6 d5 z3 \$ |/ @& W) S name would result in an invalid file or directory name. The name provided here2 B5 w& F( V3 `
is used as the directory name (within the zip) and the prefix for the key and
5 i- Q5 ^6 W& ^ certificate files. The filename is required if you are prompted and the name
; C3 w: J+ E* N is not displayed in the prompt.2 ~4 R7 V& `6 S' z
* IP addresses and DNS names are optional. Multiple values can be specified as a
) l, @+ ]( x5 I/ L: \) Q, [ comma separated string. If no IP addresses or DNS names are provided, you may8 H+ R/ {5 A/ o: ^1 T2 \0 u) E5 O
disable hostname verification in your SSL configuration.. a" K9 P+ ?% G& j/ z- C$ A3 p% X
& L: n8 h" d! C/ G, ~3 q
% A! B' S. b* @5 B * All certificates generated by this tool will be signed by a certificate authority (CA)
( S# H1 K: f7 i3 U unless the --self-signed command line option is specified.
) }5 |' D. e {! \5 @ The tool can automatically generate a new CA for you, or you can provide your own with7 J" l! e% R' u! V& `
the --ca or --ca-cert command line options.. |7 ~" m% o e } J9 a8 G
# J. N% v" E; G! L% t; p7 O D9 M
0 z' R! F5 j* O4 k7 NBy default the 'cert' mode produces a single PKCS#12 output file which holds:
2 c0 \% r. ?( ^( t* D& a * The instance certificate
0 u2 b! g/ T' p% \, t+ {* t * The private key for the instance certificate
4 r7 c, t. O* d * The CA certificate, Y4 \) U7 o% r6 l4 G% j: m
9 D |# [$ ^, dIf you specify any of the following options:
3 m6 U4 z3 P! a$ b * -pem (PEM formatted output)) e* [& `6 ~& I7 v% k7 v
* -multiple (generate multiple certificates)" p1 i" [! s7 w! v @
* -in (generate certificates from an input file)
- M5 u. d7 ]4 } t8 Ythen the output will be be a zip file containing individual certificate/key files
( E: U q! r/ @" F
4 n! s) K9 O, i& r+ y3 l* g6 IEnter password for CA (elastic-stack-ca.p12) : 【输入密码】
6 S5 e a0 T* r: J1 TPlease enter the desired output file [elastic-certificates.p12]: 【直接回车】8 s9 U# }) z8 B p! I
Enter password for elastic-certificates.p12 : 【再次输入密码】. i( S/ f) f' x2 n4 Z' \
+ s0 ~1 c& P' u. u1 R P1 X0 |
Certificates written to /data/elasticsearch/elastic-cluster1/elasticsearch-8.15.0/elastic-certificates.p12
7 E" f: \4 n* Z* T5 Y) Q$ O& \6 \8 R% h2 h X j- @
This file should be properly secured as it contains the private key for 3 M! L9 @+ i( M9 F% |0 X
your instance.
. q( d2 S, L3 e( V" AThis file is a self contained file and can be copied and used 'as is'0 G0 w" n) J( b$ x
For each Elastic product that you wish to configure, you should copy) t/ }* g `; x* Y- F' K
this '.p12' file to the relevant configuration directory
3 X" T0 B2 l a4 l, r9 }; Aand then follow the SSL configuration instructions in the product guide. ~0 h* G0 b4 s8 U4 i; t
8 ?7 e$ {2 \. @% l
For client applications, you may only need to copy the CA certificate and
# m# X3 D2 V6 S g% ?& tconfigure the client to trust this certificate.
% l! t& s! q( r$ U
9 D2 n. `, c I2 G' J7 e
' u5 c( J O7 N% q
& w' m* h0 a5 I( `+ A[es@it-elassearch-2 elasticsearch-8.15.0]$ ./bin/elasticsearch-certutil cert --ca elastic-stack-ca.p12
6 k7 c# H/ ?* h& H. sThis tool assists you in the generation of X.509 certificates and certificate) A. @. z' P' t+ ~1 p: y& _
signing requests for use with SSL/TLS in the Elastic stack." h: b2 m1 u- p* d9 `
2 `+ P: F( q1 r, D: F, [& xThe 'cert' mode generates X.509 certificate and private keys.) U1 h! s- v9 H* e4 i
* By default, this generates a single certificate and key for use0 K" B6 P+ a4 n4 c1 J
on a single instance./ Y7 S# g5 N8 a0 F) N
* The '-multiple' option will prompt you to enter details for multiple
8 h; n' d% f: Q& O* \ instances and will generate a certificate and key for each one
4 d' l) h! S9 ` * The '-in' option allows for the certificate generation to be automated by describing
4 |; n8 O, r* a6 M( L the details of each instance in a YAML file
f0 p$ j- V8 v( X. @
* X5 k$ @# F6 {. G, G7 V * An instance is any piece of the Elastic Stack that requires an SSL certificate.6 e! `4 f1 c# I- ^3 o @8 M# U
Depending on your configuration, Elasticsearch, Logstash, Kibana, and Beats5 Y$ c* B4 @3 A! P% P7 I8 t
may all require a certificate and private key.8 `7 Y- s' h1 v' ~( I( F& K
* The minimum required value for each instance is a name. This can simply be the
/ N3 }( d# V" P8 J0 K' I hostname, which will be used as the Common Name of the certificate. A full
! J$ v* x$ Z" ]1 R* F distinguished name may also be used.- Y) x7 D, G% w! N6 M8 ~
* A filename value may be required for each instance. This is necessary when the
3 H0 y: \3 P6 M" H* Y( O name would result in an invalid file or directory name. The name provided here7 R; }4 s* r6 k$ k/ M8 D
is used as the directory name (within the zip) and the prefix for the key and
" W0 M% o: g; k$ r9 J q& N certificate files. The filename is required if you are prompted and the name4 v( h0 F- p; G; k7 Y. A' c
is not displayed in the prompt.
" Y. F: ^/ @" m9 ~- o- |* X" x * IP addresses and DNS names are optional. Multiple values can be specified as a: m; u4 t0 y! D: O6 |6 ?
comma separated string. If no IP addresses or DNS names are provided, you may3 [$ k0 }" \: F( ]
disable hostname verification in your SSL configuration.
; Z: Q; _' _9 x6 L% H0 J) K% u( o* b6 Q- z4 O
9 @: v7 r5 B* l( m: a8 O9 u4 e
* All certificates generated by this tool will be signed by a certificate authority (CA)
; ?' h5 q5 O/ _5 r- q, U unless the --self-signed command line option is specified.
! A0 B6 x( [; ]. d7 [) \ The tool can automatically generate a new CA for you, or you can provide your own with$ V2 P8 P: @8 e
the --ca or --ca-cert command line options.' S. O" C% w6 @* A
: Q4 i1 k- U; Y
! b* S( A7 A. j2 G( _) W3 m
By default the 'cert' mode produces a single PKCS#12 output file which holds:
4 z. z2 d5 ^3 ~) D2 n" h/ m * The instance certificate
' ~1 w" ^/ m- h8 T * The private key for the instance certificate" l: n; i: c% j2 B$ K9 Z: x& O- x
* The CA certificate) Q$ h l r, E7 U( ]) }% B
# _) N* C6 o% X' W6 h; e% V( @- N, y3 A
If you specify any of the following options:
. \; i/ G9 O0 Q5 H8 Y' F0 z * -pem (PEM formatted output)
3 {/ V3 t" s& r. s! S- Y: \ * -multiple (generate multiple certificates)0 ?- d9 t& U9 E" P, S3 F" V! E* W
* -in (generate certificates from an input file)# [/ X) H* M. h$ t& N7 ~; ^
then the output will be be a zip file containing individual certificate/key files8 w- \ D( `( i) t8 S6 O
# [: O" D' m$ ~& O
Enter password for CA (elastic-stack-ca.p12) : 【输入密码】
T' ]+ t5 {2 `% ]) k2 mPlease enter the desired output file [elastic-certificates.p12]: 【直接回车】
2 W2 a; J; l% W. GEnter password for elastic-certificates.p12 : 【输入密码】0 j# N1 E6 t3 _1 h( p! t, [
2 G4 H5 S, Y4 i7 P% g
Certificates written to /data/elasticsearch/elastic-cluster2/elasticsearch-8.15.0/elastic-certificates.p12% x; _/ j2 t( ^. D; X
0 s7 x! N9 u3 S, ?This file should be properly secured as it contains the private key for
! w% V: A. D& \9 h6 d2 I8 F: }% Gyour instance.( H! N3 m: B- R: {
This file is a self contained file and can be copied and used 'as is'
; D. F! b% _- M8 r; y+ j. S5 tFor each Elastic product that you wish to configure, you should copy+ E( @7 N6 O: r q
this '.p12' file to the relevant configuration directory
* L8 D( l3 p2 e! Eand then follow the SSL configuration instructions in the product guide.: g: P1 f- C8 ^) X9 D2 r; i% r7 ~
8 O) w4 @* d' ]+ ]2 d% eFor client applications, you may only need to copy the CA certificate and
5 M4 R; x" M7 z. q$ A3 Kconfigure the client to trust this certificate.
. \# b6 e. _4 T* f* s5 B; s# R6 a& Q4 L4 K* O
: q, N+ v2 M" a. o' D
##将凭证迁移到指定的目录：+ `' |% [4 h j3 P
创建目录：+ q3 p$ j1 }. N: x+ L( I
mkdir -p ./config/certificates/
4 ?# E7 E( M; u' x& a移动凭证到指定目录下：
! g0 S8 b( `; k* {9 L: Tmv elastic-certificates.p12 ./config/certificates/
& L, [/ f& i% L1 i, ^
! F1 J& [, w- W9 m, s赋于权限：
: h0 a- @ @4 C1 o
) C4 t/ x- `: c7 Z4 g. w# m% _2 L4 g* B P
[es@it-elassearch elasticsearch-8.15.0]$ rsync -azvP -e 'ssh -p 22' config/certificates/elastic-certificates.p12 es@172.24.110.126:/data/elasticsearch/elastic-cluster2/elasticsearch-8.15.0/config/certificates/elastic-certificates.p12 T% [2 q4 _9 X8 `
The authenticity of host '[172.24.110.126]:22 ([172.24.110.126]:22)' can't be established.$ p2 F! J2 c4 W8 D
ECDSA key fingerprint is SHA256:Tvzi0ICzurMYEPySzerkOmwk/o7XHxmABVKRigofHzg.0 B( I! g1 f! S; [9 [# A* w% o" T
ECDSA key fingerprint is MD5:f0:92:26:fd:da:d3:e4:db:be:36:b1:fe:d6:2b:65:25.
' R3 z2 b0 Z0 E6 `; h; a' dAre you sure you want to continue connecting (yes/no)? yes+ i9 g" s- {7 A5 i9 K6 F
Warning: Permanently added '[172.24.110.126]:22' (ECDSA) to the list of known hosts.7 a! T* D1 o1 g9 b! }% T2 {
es@172.24.110.126's password:
* Y+ i+ U6 J8 X; O8 Q: qsending incremental file list
; i- Z3 Z3 }2 Y1 Felastic-certificates.p12
! g6 P+ u9 {: U% i 3,596 100% 0.00kB/s 0:00:00 (xfr#1, to-chk=0/1)
: o8 z% h% }3 @. \3 ?9 `) [: R% E) u; X$ K/ l5 m
' P+ o; M: R, U# i
sent 3,631 bytes received 35 bytes 564.00 bytes/sec8 H/ R0 F# R a2 Z( ]) V8 M( s
total size is 3,596 speedup is 0.98/ ] B- p- }' S" `
9 g* F9 f) u$ O6 X, P7 P1 N: I
修改配置文件（每台都需要添加）: ~' W8 M3 U: e
5 l3 H* H* C6 }
1 t, ?. T m k" m2 }, `
http.cors.enabled: true
) B+ t& \* y& ^. X) u$ lhttp.cors.allow-origin: "*"( k& Y2 A6 f, {) |8 j- A/ E+ q
http.cors.allow-headers: Authorization,X-Requested-With,Content-Type,Content-Length
3 H: x1 _# Z6 `2 q5 [
- T/ l4 l% |7 k9 ]1 w; C% m
+ M3 p; X2 ^% X" ~xpack.security.enabled: true* `9 m2 L& q- q0 X' i- L
xpack.security.authc.accept_default_password: true8 C; D* H. s! x# i. ]9 |3 A* Q' e8 H
xpack.security.transport.ssl.enabled: true- \: {2 f7 Q3 e; o! Y9 d1 t# [
xpack.security.transport.ssl.verification_mode: certificate
& I& q+ f) V6 A2 r. ~( T! v$ Txpack.security.transport.ssl.keystore.path: ./config/certificates/elastic-certificates.p12
% l0 [, ~) Q5 o" e6 t$ B2 O4 ~" oxpack.security.transport.ssl.truststore.path: ./config/certificates/elastic-certificates.p12 t) s. w+ o9 d; k% r; H
/ c! g* G$ P0 L3 E* Z0 O
. }& V4 D: _! u; k2 l4 k$ X在各个节点上添加密码：(每一台es都需要操作)
H* J" W* I3 I7 Z! ?
# d4 z* q( r5 G* q5 o+ c# U+ ]% [; h1 [) U) b9 u. o9 h
" C; C8 @4 `8 Y' {/ _8 u7 g) @ u4 N. i2 }, G$ h. W" R* t
# b. R4 O/ R" F1 F* T- M4 E加权一样需要切换到es账号：3 h0 H2 r2 k! p+ S. z0 @# e( R
! L* L$ ?/ V) P0 b A) M, d. p/ ?6 R在各个节点上添加密码：3 }# Z9 r) k2 \) Z; t( W7 A
% _: g. ~ A' ]* S+ f" z
[es@it-elassearch elasticsearch-8.15.0]$ ./bin/elasticsearch-keystore add xpack.security.transport.ssl.keystore.secure_password
- v0 c8 w, W* p[es@it-elassearch elasticsearch-8.15.0]$ ./bin/elasticsearch-keystore add xpack.security.transport.ssl.keystore.secure_password
; z! d& t( |, a. p4 p0 aEnter value for xpack.security.transport.ssl.keystore.secure_password:9 H, D& s2 u/ x
8 e0 q. k! [* p# v5 f( i
, C8 \* H+ i# W5 y* c[es@it-elassearch-2 elasticsearch-8.15.0]$ ./bin/elasticsearch-keystore add xpack.security.transport.ssl.keystore.secure_password6 b" e2 {# V2 \4 H/ O. d' B
Enter value for xpack.security.transport.ssl.keystore.secure_password:- E' n: Z% H' D1 U
输入密码：第一次输入密码( P* ?9 m2 a, V% U% \+ b# V
: E) G2 h! w* n; v4 [: o
[es@it-elassearch elasticsearch-8.15.0]$ ./bin/elasticsearch-keystore add xpack.security.transport.ssl.truststore.secure_password. U9 F, B3 k( R6 t
Enter value for xpack.security.transport.ssl.truststore.secure_password:" F) B( f* b/ \
1 e& ^# P( n, C% }8 [/ B5 s( t4 Y# E[es@it-elassearch-2 elasticsearch-8.15.0]$ ./bin/elasticsearch-keystore add xpack.security.transport.ssl.truststore.secure_password! ]3 i/ e! q1 u' h9 p6 C- v
Enter value for xpack.security.transport.ssl.truststore.secure_password:
9 V4 M/ y1 N3 N2 {, w; d( Q! Y3 m) v5 w6 i3 g/ d
) }& o$ ^1 ]1 C. J, Q% P
输入密码： 第二次输入上面的密码：/ [: _" b# o! e S5 ^' q5 I
0 q$ P1 }* U' ?$ c: d( e4 Q% r: B0 Q9 n/ I
4 s3 n! ~. v9 W! { ]
/ W1 H& t8 O# C$ }8 r- ?6 V S
接下来和没有做鉴权的一样，逐个启动集群：' j, _5 T8 G* u* H
5 L! M/ C7 n* j+ ?. c" X$ T/ j) X0 n: d: U" B- Z
' n% ^4 }! e$ N( W, p* [
切换到其它用户，root用户不能启动ES：su es6 ?& r" U' P% O5 E0 f
2 x9 ~( [% x9 q/ S5 s1 G, \$ j; G$ g
" \* f! F' [! r! W, l
) A3 i( q& N, U, Rbin/elasticsearch -d4 Q V" C0 E7 C7 x, Z
[es@it-elassearch elasticsearch-8.15.0]$ bin/elasticsearch -d; G- _; o# }4 V9 z% {3 g. J i7 V
8 A; `/ N' `8 h# u0 ?8 l) f7 U& g7 h! D4 p* G
9 Q G0 I8 |' P! U
4 B+ c" Z1 m. u$ r, C$ ]6 @6 s6 a6 w# i7 n
|
|
发表于 2024-10-31 15:00:04