|
|
启动集群：
5 j' H) o r+ T/ y
4 t5 M1 U, }6 K. u+ F2 X前提：设置好系统配置和JVM堆内存6 H/ X/ y* u* P! }7 ]) `5 Q0 s
. x$ Q+ O$ U/ F
创建elastic的数据和日志存放目录，如果是测试环境无所谓，如果是生成环境一定要单独设置数据和日志存放的路径，因为ES可能因为升级或其它原因把原有的数据清理或丢失等因素
; G* ~/ }5 a* f' ]+ C7 c2 M& y* A' T/ \" f- z4 L
( {, v2 _" r$ r* v/ s* D1 F
+ o, h: ~! _$ y2 p% A8 S8 }. F% o3 J
配置文件属组权限，并启动7 Z) T9 E, K: l# d% A8 \
[root@it-elassearch elasticsearch]# chown -R es:es elastic-cluster1/1 u* j8 i. j" E: f& p
[root@it-elassearch-2 elasticsearch]# chown -R es:es elastic-cluster2/6 \; `, A% O2 K5 B2 J
6 B6 K: @' R0 r7 J3 D. L- Y- ^' ^7 C) m
9 Y' X) i! O0 v; |' D$ B% u如果添加鉴权配置请按照此处配置，不配置即可略过：
8 D, d% t6 t* e2 ?: m; q0 X! Q' h
8 i7 X' G; p7 |) k; P, x4 O
$ |. P8 W( ?0 q4 w, C- I0 F2 d生成密匙：
$ O/ E3 q- D6 g* B K0 r7 H/ D[es@it-elassearch elasticsearch-8.15.0]$ ./bin/elasticsearch-certutil ca
+ Y- r# G" K6 h: t' Z7 m7 ?; n; hThis tool assists you in the generation of X.509 certificates and certificate
! y# K( R2 I* ^$ N, Xsigning requests for use with SSL/TLS in the Elastic stack.
! D3 s1 ?; o9 J! d! p) X: |' S) x! C, q, h3 [; T0 Z
+ l4 h: O, \( \" z4 V
The 'ca' mode generates a new 'certificate authority'
+ F/ V6 v% \$ I$ F6 S* s" YThis will create a new X.509 certificate and private key that can be used- D9 J+ u# _. [4 y: P! C# |0 g% m
to sign certificate when running in 'cert' mode.' B3 R3 ?$ G4 Y; a
* B# {& o% n" ?1 d! [- c a! x# v: N' ~% v, p( \3 q8 D4 B
Use the 'ca-dn' option if you wish to configure the 'distinguished name'
; p! a! _$ j8 Cof the certificate authority
4 a8 J8 ~. l7 M
. E4 l- k# ]; P, R0 E. x" W
( x6 v* k1 @0 F0 J- j3 S9 uBy default the 'ca' mode produces a single PKCS#12 output file which holds:# M& e/ [) L# _: y& y& r
* The CA certificate3 t* D/ b+ m0 C5 j- |( N
* The CA's private key3 s- J E6 Z) Q7 T4 S! F A8 e! w
. m/ i T" g+ c5 }, B
. b- z& r. x( c1 @9 s1 d+ V' y4 T
If you elect to generate PEM format certificates (the -pem option), then the output will% D& u ^% z# G8 q; n5 d: M
be a zip file containing individual files for the CA certificate and private key
7 `' \9 t' d; j- A3 w# i
3 P" B2 B [* PPlease enter the desired output file [elastic-stack-ca.p12]: 【这里忽略，直接回车进入下面输入密码：】- |0 X. p0 C- g: n/ A; f
Enter password for elastic-stack-ca.p12 : 【输入密码】
% ?" U* b: G) p; |( r. J
' m. s& W( C' t4 [) Q. d; M6 M- y# e! W( F, P- [0 T& i/ @
1 e" D7 Q3 i3 ^6 s% T
[es@it-elassearch elasticsearch-8.15.0]$ ll! u/ Q2 S8 L8 R6 f Y
total 2268
5 x' [2 @( w+ ?4 F( ~: J0 V......
& G3 V& O) E; y( _-rw------- 1 es es 2672 Oct 28 17:05 elastic-stack-ca.p120 Q, F! D2 J2 Q$ Z' g
......
0 R+ v$ t# F5 Q
7 n9 }# W( Y2 O- N1 L6 \1 [8 P! Z9 ?% R: k2 S8 g$ ~
# T! R, X$ D, w0 i: N
) x E* F$ R# C8 O" A3 @- V8 P, X$ D0 @5 \: \ [/ z6 |, O% z
# J+ ?9 S, t: s0 M% G" b$ d+ Y
[es@it-elassearch-2 elasticsearch-8.15.0]$ ./bin/elasticsearch-certutil ca! `* A6 X7 Z( ]
This tool assists you in the generation of X.509 certificates and certificate
! M) f/ ^6 l' qsigning requests for use with SSL/TLS in the Elastic stack.
( @& J" R. z& p# L3 E
) x; y# Q- a5 w* t9 ? ]
6 E! s* a/ {# e. ]& ~; `* PThe 'ca' mode generates a new 'certificate authority'
1 ^9 c: `( a" K% T6 W% _% pThis will create a new X.509 certificate and private key that can be used4 x$ {5 F) Z6 A+ ]! e& ~/ r
to sign certificate when running in 'cert' mode.* z& H' t2 ^+ C. { n, C
! Q) z) A' m4 E4 w2 m; j
: c& F, t; U# x, _6 X+ @% BUse the 'ca-dn' option if you wish to configure the 'distinguished name'
$ U4 l( P! u( @5 G5 {. Eof the certificate authority8 [3 T2 v3 w# B* n5 B! v7 ^
& K; ^# v1 _# b" j
2 W5 Z6 d- R( d2 HBy default the 'ca' mode produces a single PKCS#12 output file which holds:& X2 M' ?/ Q2 _. {/ o& ]' w6 w/ U. q; A
* The CA certificate) J9 H d- ]; Y+ D/ Y
* The CA's private key7 w5 C1 o0 y2 i* J. ]
# b, v9 v8 J) d; E9 o
% r- O* j4 z7 ?5 u- t% DIf you elect to generate PEM format certificates (the -pem option), then the output will
2 |3 U, h2 j9 h3 R9 tbe a zip file containing individual files for the CA certificate and private key7 U6 X% l, d& w6 {
5 Y; H' U5 H7 Q1 N; e& F7 S$ l
. N8 m% Y) h4 o$ b$ {Please enter the desired output file [elastic-stack-ca.p12]:( x& U# I$ Y: y0 W/ M6 X( R
Enter password for elastic-stack-ca.p12 :% J2 V7 v" T) O- s
0 f2 t& d$ \9 M8 y1 H8 B, z+ z
4 t' k- y- F: W2 ]3 {4 B. {9 G. L
生成密钥：, g3 m9 _: \; p
: i" {2 d& g+ a6 e
/ L4 u0 `3 \* ?+ ~. b! ~( K[es@it-elassearch elasticsearch-8.15.0]$ ./bin/elasticsearch-certutil cert --ca elastic-stack-ca.p12
" A2 S8 }( U9 GThis tool assists you in the generation of X.509 certificates and certificate3 ? V# \( c& \6 j1 r( i: E
signing requests for use with SSL/TLS in the Elastic stack.+ [) L+ Y0 U; \$ x" L8 a! L4 z' y
, W$ _7 d1 q0 x) ?' }- `) J5 Z
The 'cert' mode generates X.509 certificate and private keys.
& z: }! T' J$ n/ E, @4 j' x# n * By default, this generates a single certificate and key for use! U8 q5 r1 o- x. C6 C3 ?
on a single instance.9 K) a3 b; x4 p! [, I' p( n
* The '-multiple' option will prompt you to enter details for multiple8 A. H. d" z' Q( u, X* D/ G+ g
instances and will generate a certificate and key for each one/ J& M# \4 \" v6 @% |3 p
* The '-in' option allows for the certificate generation to be automated by describing
+ r: {# L# y$ P+ U @- b$ e the details of each instance in a YAML file
# L& _& K! ]" z' }7 f: z4 |9 s: n, V1 m" P, W9 W0 `# t4 O
* An instance is any piece of the Elastic Stack that requires an SSL certificate.- h l1 N! x& F0 x1 d
Depending on your configuration, Elasticsearch, Logstash, Kibana, and Beats
; V$ w$ Y, @, |, t! Q' A0 ^; D$ I6 q may all require a certificate and private key.4 s& P [. i; l$ K I% H
* The minimum required value for each instance is a name. This can simply be the
# i8 \0 e1 S Q, W4 X( ~ hostname, which will be used as the Common Name of the certificate. A full
$ y% T+ P6 v/ ]/ z distinguished name may also be used.
$ P* c( _ `* c * A filename value may be required for each instance. This is necessary when the$ P9 M. p1 V2 i& F5 U" D8 ? H
name would result in an invalid file or directory name. The name provided here
. {& t: M* V+ c+ a& Z/ ?" M* h, v, Y is used as the directory name (within the zip) and the prefix for the key and
) O$ `+ F3 s6 { certificate files. The filename is required if you are prompted and the name
: f! O0 r# z7 A5 @; o9 W" ] is not displayed in the prompt.
- [. g8 J2 @( @5 w% j- O * IP addresses and DNS names are optional. Multiple values can be specified as a: \4 O: `' c7 w/ c0 w; G
comma separated string. If no IP addresses or DNS names are provided, you may
# Q A4 P! q# h8 ]+ T disable hostname verification in your SSL configuration.
" j9 g& V* O- o7 l g/ J( u
7 @+ d, l2 _+ Z9 a- D+ s& f3 H0 M3 z( D1 E1 J
* All certificates generated by this tool will be signed by a certificate authority (CA)
+ A( g' ?; Q5 J! v+ B1 u) j/ E unless the --self-signed command line option is specified.! |9 P3 c9 A% c: W
The tool can automatically generate a new CA for you, or you can provide your own with
6 R/ Q1 }+ e) f0 j; W- o the --ca or --ca-cert command line options.* K3 h& F+ F2 ~, a
% v( v# E7 p$ A6 V" M3 Z* c: O* T; T3 E. _" @
By default the 'cert' mode produces a single PKCS#12 output file which holds:2 M2 v! `* k6 f' N' M' ?' W
* The instance certificate
) y9 F0 J4 x0 @7 U& M * The private key for the instance certificate' v2 T9 d1 l$ L! _% g
* The CA certificate& u0 ^& X# R9 ~" F$ z [& G/ L
0 A1 s! @4 x4 | k( H
If you specify any of the following options:* ~9 Y7 q5 Q( E
* -pem (PEM formatted output)' M6 `: `# M3 \
* -multiple (generate multiple certificates)- i6 l& U/ F+ O6 r/ j9 C3 d* M" p
* -in (generate certificates from an input file)4 L0 c5 }0 w$ |
then the output will be be a zip file containing individual certificate/key files* W; N4 ?# d% o8 E7 G# B
! R( n8 d% A( o2 R: ?Enter password for CA (elastic-stack-ca.p12) : 【输入密码】, c6 R- |$ s$ N; U% d
Please enter the desired output file [elastic-certificates.p12]: 【直接回车】% D( ]/ k& F1 X
Enter password for elastic-certificates.p12 : 【再次输入密码】
& W" b' \1 ?) P! Z
+ {6 S$ a! M. u. B7 B6 bCertificates written to /data/elasticsearch/elastic-cluster1/elasticsearch-8.15.0/elastic-certificates.p12
2 y; Q6 }( p& B. B# D
- m {0 F0 L8 G: E- k+ gThis file should be properly secured as it contains the private key for
& o* l9 w0 p" C4 \9 Y. s8 v4 vyour instance.2 ^5 G% w1 [; N/ V
This file is a self contained file and can be copied and used 'as is'
# |/ M" j, O# h4 f6 d4 z' EFor each Elastic product that you wish to configure, you should copy" Y8 j+ P, C6 g: r2 Y
this '.p12' file to the relevant configuration directory
+ [; x3 j" G$ F7 g( j' xand then follow the SSL configuration instructions in the product guide.
' ]( k4 W. u$ s' k7 [; c
' G. c9 {, Y* T4 ZFor client applications, you may only need to copy the CA certificate and- w( R' N! p! W
configure the client to trust this certificate.
- V% s8 C* b. B8 Y! A
4 g1 c6 M) Y5 U q: s
1 F8 U8 f* P% s3 I
3 \ b( ~5 d/ F9 S1 B- t[es@it-elassearch-2 elasticsearch-8.15.0]$ ./bin/elasticsearch-certutil cert --ca elastic-stack-ca.p12 - q' p3 F: Z, W0 d8 J9 P5 g) z
This tool assists you in the generation of X.509 certificates and certificate
3 l4 ^# [: L; ]0 S% z% n7 Msigning requests for use with SSL/TLS in the Elastic stack.
; q% o f1 R5 R
4 _ X. \1 V* L/ j; HThe 'cert' mode generates X.509 certificate and private keys.) G& q5 a( i2 X% o) J, d D! o& P
* By default, this generates a single certificate and key for use
1 Y, T5 x- [1 g6 U on a single instance.6 m7 _) j5 H3 Y8 L) L
* The '-multiple' option will prompt you to enter details for multiple
, b7 b8 l+ \: Q" K7 |) r instances and will generate a certificate and key for each one
8 u9 }' m$ z2 Z& l. } * The '-in' option allows for the certificate generation to be automated by describing# G# e" \% s8 S) T& |- Q* {, F
the details of each instance in a YAML file
; H: r$ |" y" e \* ~- R. P
& R: s/ i/ ~/ O * An instance is any piece of the Elastic Stack that requires an SSL certificate.2 u/ f1 `6 G6 P! b! }2 W- d0 b3 ~/ A
Depending on your configuration, Elasticsearch, Logstash, Kibana, and Beats
& w6 g) ?2 J8 ]! C# [7 [ may all require a certificate and private key.3 I0 i7 a, }* P. |5 U2 Z% T
* The minimum required value for each instance is a name. This can simply be the
* p' X$ N& ]. C hostname, which will be used as the Common Name of the certificate. A full
/ y( P9 m: w) ]" M1 A7 L) t. s- i distinguished name may also be used.
8 Q1 B4 y; @9 H" N * A filename value may be required for each instance. This is necessary when the$ y) P$ C) F& s# |! ~: m
name would result in an invalid file or directory name. The name provided here
" W. N1 |% S# I; E$ ]% r is used as the directory name (within the zip) and the prefix for the key and/ A0 H+ r$ v1 ?4 k- m Y" ~0 i
certificate files. The filename is required if you are prompted and the name
; p7 h" ^ @3 d/ t5 @" s, R W is not displayed in the prompt.
9 t8 J4 |( J1 N- ~+ c4 V/ |( _ * IP addresses and DNS names are optional. Multiple values can be specified as a/ u. N$ D/ Q2 T+ J- E# ~& h
comma separated string. If no IP addresses or DNS names are provided, you may
! A7 y8 k8 F+ Y disable hostname verification in your SSL configuration.6 Z( n# \6 v, {; j* d2 m5 K- W
, B$ j8 b; F2 ]/ [7 W3 f9 c4 A$ F) s n$ w
* All certificates generated by this tool will be signed by a certificate authority (CA): c9 V8 \8 [* V$ l: p" Q; P: |# {& s
unless the --self-signed command line option is specified.: F0 |! ^; N. p+ P* P" H' N
The tool can automatically generate a new CA for you, or you can provide your own with* E8 J) L+ z( t+ m) i3 f* d
the --ca or --ca-cert command line options.
, r# g3 ^8 y6 f+ v* b% h# |6 \5 K' R6 C e [" x t( h; ]. l
) B3 C3 B8 }- f+ gBy default the 'cert' mode produces a single PKCS#12 output file which holds:6 X N, F& |" ]: [
* The instance certificate
5 D& R A- U$ A- d; e: \ * The private key for the instance certificate
1 M& ]$ |8 r. F4 P" [ * The CA certificate
; I2 e# |7 z& s; r; r5 B
0 I* R( V( l! r- C6 E# e* bIf you specify any of the following options:4 C, n. i& d" _' O0 ~) |8 z
* -pem (PEM formatted output)
8 S% k' t! @% l7 q/ f * -multiple (generate multiple certificates)" T" g- z+ H8 j6 m& ~( i2 X' D# I! e
* -in (generate certificates from an input file)6 h0 P8 M7 ^) t- q$ ^2 J
then the output will be be a zip file containing individual certificate/key files/ |! W* L( T! i1 l* t
1 f+ C0 u: y, L2 w7 XEnter password for CA (elastic-stack-ca.p12) : 【输入密码】
3 j$ w7 t1 d! I5 j8 n& j& w4 APlease enter the desired output file [elastic-certificates.p12]: 【直接回车】! }& s& X# ]( C" d
Enter password for elastic-certificates.p12 : 【输入密码】6 m6 }; Y* m; P7 s0 u0 J$ U5 a9 w$ U
3 c, |2 A; S4 o0 \ ^1 m
Certificates written to /data/elasticsearch/elastic-cluster2/elasticsearch-8.15.0/elastic-certificates.p12, ^, b; P, h3 `* {# m6 u: l
4 ?0 r6 Q5 k* j/ h/ I2 C9 @$ h9 s! J
This file should be properly secured as it contains the private key for
" R2 i* d& c7 z0 }your instance.
! }' a7 X- v* f. z* j, O0 aThis file is a self contained file and can be copied and used 'as is'
/ |( ?# L, q8 ~! y7 H5 b. D6 lFor each Elastic product that you wish to configure, you should copy: j: K" q- J4 ^! ?
this '.p12' file to the relevant configuration directory
$ W1 b. |9 k+ e& K* E4 s6 _* zand then follow the SSL configuration instructions in the product guide." F6 R# {/ f1 B1 `
+ I: J4 W9 r9 v& b: {
For client applications, you may only need to copy the CA certificate and$ k& Z4 b7 D- Y [
configure the client to trust this certificate.
! W2 F2 E, y% s+ a9 F
5 j) ~( u: J4 i5 a- k
: X1 \- z( s: E1 l% f##将凭证迁移到指定的目录：
3 i9 W! |2 I3 @0 H: x- J创建目录：
2 x- `' N# g, i x1 R% D. U, \ mkdir -p ./config/certificates/
5 K3 ]- [8 J2 V" W移动凭证到指定目录下：
2 q8 X- e3 r% }! }3 A W# ~mv elastic-certificates.p12 ./config/certificates/
% ]4 w r3 A& ~; ?) h& H! m. J7 } G+ t
赋于权限：5 P/ f5 ` T4 Z4 b- x: z/ O
2 ]0 C/ |. R7 L0 _$ @
- b, P. \0 _) \) x+ z[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
! ~) w8 V! f+ k3 \9 g8 \2 u7 P9 J* CThe authenticity of host '[172.24.110.126]:22 ([172.24.110.126]:22)' can't be established.
" y- B) s. V$ f- H$ uECDSA key fingerprint is SHA256:Tvzi0ICzurMYEPySzerkOmwk/o7XHxmABVKRigofHzg.2 ^. K3 X2 I9 g2 X3 s2 @0 h; @
ECDSA key fingerprint is MD5:f0:92:26:fd:da:d3:e4:db:be:36:b1:fe:d6:2b:65:25.& |" W0 C1 C9 |" s3 A7 z
Are you sure you want to continue connecting (yes/no)? yes
# ^) \1 |3 P1 T" H1 ?7 G. YWarning: Permanently added '[172.24.110.126]:22' (ECDSA) to the list of known hosts.! W+ f. u! m5 ]3 E' F- U1 g8 C9 ~
es@172.24.110.126's password:
! m7 l; P4 f3 Y* f. Bsending incremental file list' P) A! {) F3 f- R
elastic-certificates.p12! R4 u. s& c0 x0 q; K& i) ^
3,596 100% 0.00kB/s 0:00:00 (xfr#1, to-chk=0/1)
: h+ x# B6 @+ m# K+ @4 ?+ w6 i4 s( @0 j8 s% o. w) e
A# \% N3 o! a0 |
sent 3,631 bytes received 35 bytes 564.00 bytes/sec9 N5 C" O' H5 [
total size is 3,596 speedup is 0.98% \, k8 @# I. G9 k$ {, l1 Y
! v% {5 j( z9 W8 u& Z4 S修改配置文件（每台都需要添加）+ w; e/ P! K' k* {
. x& e! V9 {/ B, f" Y1 b3 Y
* v4 R N& A5 F: Uhttp.cors.enabled: true
$ }$ c9 W' t9 }* t9 L' |/ ehttp.cors.allow-origin: "*"" \0 {; E5 x' @, j6 `8 `
http.cors.allow-headers: Authorization,X-Requested-With,Content-Type,Content-Length `* j8 a x- N0 |0 K$ A
# `! a3 ?: w' j2 l6 `
' @: u. ~4 l1 G, q" ~xpack.security.enabled: true
7 N! f0 g+ \5 W7 A) sxpack.security.authc.accept_default_password: true
; k+ o$ k7 F/ F# R0 Qxpack.security.transport.ssl.enabled: true, x# k7 l, c& v5 @
xpack.security.transport.ssl.verification_mode: certificate
4 V @2 w* f2 j' ?xpack.security.transport.ssl.keystore.path: ./config/certificates/elastic-certificates.p12
0 T3 M$ Q9 w+ m9 i- [, Expack.security.transport.ssl.truststore.path: ./config/certificates/elastic-certificates.p12
& ]" v# L3 a X7 G' e A* W* p0 J( w: v/ s( ^9 b
: C3 A8 U% W- `5 N
在各个节点上添加密码：(每一台es都需要操作)" D! [, a6 x; q0 L
! @" B0 W- R o
9 w6 t+ N, D9 t( @4 }& u& N% O7 S! f# k6 a
1 _. E6 b' j% w) m* z, ^# C' Z1 O
加权一样需要切换到es账号：+ @- u6 y' W( g5 e2 i, q( F
' A: v, L! L% P7 W j在各个节点上添加密码：9 A& v3 K% b( u+ r! ~1 T( v
: Z# N# E: Q( H$ T1 x
[es@it-elassearch elasticsearch-8.15.0]$ ./bin/elasticsearch-keystore add xpack.security.transport.ssl.keystore.secure_password0 h. R; J' P+ {, ?/ ~- Y* R
[es@it-elassearch elasticsearch-8.15.0]$ ./bin/elasticsearch-keystore add xpack.security.transport.ssl.keystore.secure_password
+ ]' g, k' ]+ ?Enter value for xpack.security.transport.ssl.keystore.secure_password:% \ d6 m) M) A; l
0 g* C7 [' l M) I5 `5 K
, I& ]- `; b/ L2 ?$ y& m[es@it-elassearch-2 elasticsearch-8.15.0]$ ./bin/elasticsearch-keystore add xpack.security.transport.ssl.keystore.secure_password
1 ~' k. C1 F; y' DEnter value for xpack.security.transport.ssl.keystore.secure_password:1 u/ C. b- q, a+ r
输入密码：第一次输入密码
7 y8 `/ A3 I# s, ]* l4 w$ D: @ J; t" V4 l8 M, J
[es@it-elassearch elasticsearch-8.15.0]$ ./bin/elasticsearch-keystore add xpack.security.transport.ssl.truststore.secure_password
4 K6 `$ P$ z1 e, D, p I( mEnter value for xpack.security.transport.ssl.truststore.secure_password:
% ^! Q, z+ g8 ?. S8 y# ~( ^' E7 ?& Q$ Q
[es@it-elassearch-2 elasticsearch-8.15.0]$ ./bin/elasticsearch-keystore add xpack.security.transport.ssl.truststore.secure_password; C+ ]: H% d# M2 @
Enter value for xpack.security.transport.ssl.truststore.secure_password:
0 B, D. z! K; [* [2 N w' [5 ~; B, q" k3 ~
! q. v/ s' M/ q, X! o9 G# a输入密码： 第二次输入上面的密码：
, X6 i7 M/ ]7 w' R5 v# W
0 W9 M1 s# \7 H( T) E5 F$ H- A/ P. d* p/ \# d4 W, I
2 ~/ l u0 N. |
; g: X7 ~, C: t; \+ `( t. Q接下来和没有做鉴权的一样，逐个启动集群：$ X4 }4 w* I0 K# C2 u5 x
8 X; r4 N A! G8 r( ~
0 Q7 a( L) R3 \/ E& p* R8 n% Q" i( w
切换到其它用户，root用户不能启动ES：su es
6 F( A3 i. A" k9 y: [2 J& |
& J O& E1 M7 `% t8 t5 l: d* y6 V* z
6 I4 M3 i" x! U
; e- E* Z8 w0 [: T& k0 n7 ^bin/elasticsearch -d J! b$ H/ U2 b& \0 c7 l: S, t8 x
[es@it-elassearch elasticsearch-8.15.0]$ bin/elasticsearch -d
+ F! U; M( j% @% n1 ?' N0 h. t
( L6 ]$ R/ W. {! W' a! L( `7 k
6 `0 Q& l; _$ R9 ^2 M+ |3 j/ \
9 U4 {0 K& M4 }- L' t" j( h
1 n' Q$ P/ s0 S" ~6 R% I8 f% Q, L" {: l; O1 L; }" r5 s$ ]
|
|
发表于 2024-10-31 15:00:04