灰度發佈-Lua-tomcat

 

1、首先我們開啓兩個服務:

  • tomcat8080,tomcat8081。
[[email protected] apache-tomcat-9.0.24]# clear
[[email protected] apache-tomcat-9.0.24]# pwd
/home/admin/software/apache-tomcat-9.0.24
[[email protected] apache-tomcat-9.0.24]# cd .
[[email protected] apache-tomcat-9.0.24]# cd ..
[[email protected] software]# cp apache-tomcat-9.0.24 tomcat8081 -R
  • 在tomcat8081裏面,我們修改conf目錄下面的server.xml文件,注意
  • <?xml version="1.0" encoding="UTF-8"?>
    <!--
      Licensed to the Apache Software Foundation (ASF) under one or more
      contributor license agreements.  See the NOTICE file distributed with
      this work for additional information regarding copyright ownership.
      The ASF licenses this file to You under the Apache License, Version 2.0
      (the "License"); you may not use this file except in compliance with
      the License.  You may obtain a copy of the License at
    
          http://www.apache.org/licenses/LICENSE-2.0
    
      Unless required by applicable law or agreed to in writing, software
      distributed under the License is distributed on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
      See the License for the specific language governing permissions and
      limitations under the License.
    -->
    <!-- Note:  A "Server" is not itself a "Container", so you may not
         define subcomponents such as "Valves" at this level.
         Documentation at /docs/config/server.html
     -->
    <Server port="8005" shutdown="SHUTDOWN">
      <Listener className="org.apache.catalina.startup.VersionLoggerListener" />
      <!-- Security listener. Documentation at /docs/config/listeners.html
      <Listener className="org.apache.catalina.security.SecurityListener" />
      -->
      <!--APR library loader. Documentation at /docs/apr.html -->
      <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" />
      <!-- Prevent memory leaks due to use of particular java/javax APIs-->
      <Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener" />
      <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
      <Listener className="org.apache.catalina.core.ThreadLocalLeakPreventionListener" />
    
      <!-- Global JNDI resources
           Documentation at /docs/jndi-resources-howto.html
      -->
      <GlobalNamingResources>
        <!-- Editable user database that can also be used by
             UserDatabaseRealm to authenticate users
        -->
        <Resource name="UserDatabase" auth="Container"
                  type="org.apache.catalina.UserDatabase"
                  description="User database that can be updated and saved"
                  factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
                  pathname="conf/tomcat-users.xml" />
      </GlobalNamingResources>
    
      <!-- A "Service" is a collection of one or more "Connectors" that share
           a single "Container" Note:  A "Service" is not itself a "Container",
           so you may not define subcomponents such as "Valves" at this level.
           Documentation at /docs/config/service.html
       -->
      <Service name="Catalina">
    
        <!--The connectors can use a shared executor, you can define one or more named thread pools-->
        <!--
        <Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
            maxThreads="150" minSpareThreads="4"/>
        -->
    
    
        <!-- A "Connector" represents an endpoint by which requests are received
             and responses are returned. Documentation at :
             Java HTTP Connector: /docs/config/http.html
             Java AJP  Connector: /docs/config/ajp.html
             APR (HTTP/AJP) Connector: /docs/apr.html
             Define a non-SSL/TLS HTTP/1.1 Connector on port 8080
        -->
        <Connector port="8080" protocol="HTTP/1.1"
                   connectionTimeout="20000"
                   redirectPort="8443" />
        <!-- A "Connector" using the shared thread pool-->
        <!--
        <Connector executor="tomcatThreadPool"
                   port="8080" protocol="HTTP/1.1"
                   connectionTimeout="20000"
                   redirectPort="8443" />
        -->
        <!-- Define a SSL/TLS HTTP/1.1 Connector on port 8443
             This connector uses the NIO implementation. The default
             SSLImplementation will depend on the presence of the APR/native
             library and the useOpenSSL attribute of the
             AprLifecycleListener.
             Either JSSE or OpenSSL style configuration may be used regardless of
             the SSLImplementation selected. JSSE style configuration is used below.
        -->
        <!--
        <Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol"
                   maxThreads="150" SSLEnabled="true">
            <SSLHostConfig>
                <Certificate certificateKeystoreFile="conf/localhost-rsa.jks"
                             type="RSA" />
            </SSLHostConfig>
        </Connector>
        -->
        <!-- Define a SSL/TLS HTTP/1.1 Connector on port 8443 with HTTP/2
             This connector uses the APR/native implementation which always uses
             OpenSSL for TLS.
             Either JSSE or OpenSSL style configuration may be used. OpenSSL style
             configuration is used below.
        -->
        <!--
        <Connector port="8443" protocol="org.apache.coyote.http11.Http11AprProtocol"
                   maxThreads="150" SSLEnabled="true" >
            <UpgradeProtocol className="org.apache.coyote.http2.Http2Protocol" />
            <SSLHostConfig>
                <Certificate certificateKeyFile="conf/localhost-rsa-key.pem"
                             certificateFile="conf/localhost-rsa-cert.pem"
                             certificateChainFile="conf/localhost-rsa-chain.pem"
                             type="RSA" />
            </SSLHostConfig>
        </Connector>
        -->
    
        <!-- Define an AJP 1.3 Connector on port 8009 -->
        <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" />
    
    
        <!-- An Engine represents the entry point (within Catalina) that processes
             every request.  The Engine implementation for Tomcat stand alone
             analyzes the HTTP headers included with the request, and passes them
             on to the appropriate Host (virtual host).
             Documentation at /docs/config/engine.html -->
    
        <!-- You should set jvmRoute to support load-balancing via AJP ie :
        <Engine name="Catalina" defaultHost="localhost" jvmRoute="jvm1">
        -->
        <Engine name="Catalina" defaultHost="localhost">
    
          <!--For clustering, please take a look at documentation at:
              /docs/cluster-howto.html  (simple how to)
              /docs/config/cluster.html (reference documentation) -->
          <!--
          <Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/>
          -->
    
          <!-- Use the LockOutRealm to prevent attempts to guess user passwords
               via a brute-force attack -->
          <Realm className="org.apache.catalina.realm.LockOutRealm">
            <!-- This Realm uses the UserDatabase configured in the global JNDI
                 resources under the key "UserDatabase".  Any edits
                 that are performed against this UserDatabase are immediately
                 available for use by the Realm.  -->
            <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
                   resourceName="UserDatabase"/>
          </Realm>
    
          <Host name="localhost"  appBase="webapps"
                unpackWARs="true" autoDeploy="true">
    
            <!-- SingleSignOn valve, share authentication between web applications
                 Documentation at: /docs/config/valve.html -->
            <!--
            <Valve className="org.apache.catalina.authenticator.SingleSignOn" />
            -->
    
            <!-- Access log processes all example.
                 Documentation at: /docs/config/valve.html
                 Note: The pattern used is equivalent to using pattern="common" -->
            <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
                   prefix="localhost_access_log" suffix=".txt"
                   pattern="%h %l %u %t &quot;%r&quot; %s %b" />
    
          </Host>
        </Engine>
      </Service>
    </Server>
    

  • 查看監聽端口我們發現,8009,8005端口是處於監聽狀態的,爲了防止端口占用問題,我們在tomcat8081文件裏面修改server.xml文件不能只修改8080這一處。

  • 修改之後啓動發現,8080是無法啓動的,也無法訪問,查看錯誤日誌,是因爲8005端口無法開啓

  • 那麼怎麼開啓呢?找到你的JDK安裝目錄,進入到jre裏面:/usr/local/jdk1.8.0_221/jre/lib/security,進入之後修改java.security文件。

  • 原:securerandom.source=file:/dev/random 修改:securerandom.source=file:/dev/urandom

之後就可以開啓了,我們在ROOT目錄下面各創建了一個time.jsp文件,稍有差別,可通過yourip:8080/time.jsp訪問。

2、nginx配置文件

................
        server  127.0.0.1:8080;
}       
}       
server {
    listen       86;
    
    #access_log  /var/log/nginx/host.access.log  main;
    
#       proxy_set_header Host $proxy_host;
#       proxy_set_header X-Forwarded-For $http_add_x_forwarded_for;
#       root   /usr/share/nginx/html;
        content_by_lua_file /home/admin/web/lua/test.lua;
    }   
    
    
    location /hello {
        default_type 'text/plain';
        content_by_lua 'ngx.say("Hello,Lua")';
    }   
    
    location /myip {
        default_type 'text/plain';
        content_by_lua 'clientIP = ngx.req.get_headers()["remote_addr"]
                ngx.say("ClientIP :",clientIP)
        #       ngx.exec("@server")
                ';
#       ngx.exec('@server');
#       return;
    }   
    
    location @server {
        proxy_pass http://server;
        include proxy_params;
    }   
    
    location @server_test {
        proxy_pass http://server_test;
        include proxy_params;
    }   
 

2、memcached安裝:yum install memcached

簡單的開啓服務操作:memcached -u nobody -p11211 -d

(daemon)守護進程

簡單的登錄操作:telnet 127.0.0.1 11211 就可以。

3、Lua腳本編寫:


#!/usr/bin/lua
clientIP = ngx.req.get_headers()["X-Real-IP"]
if clientIP == nil then
        clientIP = ngx.req.get_headers()["X_Forwarded_For"]
end
if clientIP == nil then
        clientIP = ngx.var.remote_addr
end
        local memcached = require "resty.memcached"
        local memc,err = memcached:new()
        if not memc then
                ngx.say("failed to instantiate memc",err)
                return
        end
        local ok,err = memc:connect("127.0.0.1",11211)
        if not ok  then
                ngx.say("failed to connect: ",err)
                return
        end
        local res,flags,err = memc:get(clientIP)
        ngx.say("value key : ",res,clientIP)
        if err then
                ngx.say("failed to get clientIP",err)
                return
        end
        if res == "1" then
                ngx.exec("@server_test")
                return
        end
        ngx.exec("@server")
        return

3、需要注意的是,我們在這兒要引入相關文件。(local memcached = require "resty.memcached")

  1. wget https://github.com/agentzh/lua-resty-memcached/archive/v0.11.tar.gz
  2. tar -zxvf v0.11.tar.gz
  3. cp -r lua-resty-memcached-0.11/lib/resty /usr/local/share/lua/5.1/(具體是那個目錄,根據自己情況確定)

4、我這兒有一個報錯,是ngx.exec的,目前還沒有解決,如果你知道,可以在下面評論:

換成ngx.say()之後可以顯示不同的信息。

官網:

ngx.exec

syntax: ngx.exec(uri, args?)

context: rewrite_by_lua*, access_by_lua*, content_by_lua*

Does an internal redirect to uri with args and is similar to the echo_exec directive of the echo-nginx-module.

 ngx.exec('/some-location');
 ngx.exec('/some-location', 'a=3&b=5&c=6');
 ngx.exec('/some-location?a=3&b=5', 'c=6');

The optional second args can be used to specify extra URI query arguments, for example:

 ngx.exec("/foo", "a=3&b=hello%20world")

Alternatively, a Lua table can be passed for the args argument for ngx_lua to carry out URI escaping and string concatenation.

 ngx.exec("/foo", { a = 3, b = "hello world" })

The result is exactly the same as the previous example.

The format for the Lua table passed as the args argument is identical to the format used in the ngx.encode_args method.

Named locations are also supported but the second args argument will be ignored if present and the querystring for the new target is inherited from the referring location (if any).

GET /foo/file.php?a=hello will return "hello" and not "goodbye" in the example below

 location /foo {

 

 

2、灰度發佈好文推薦:https://cloud.tencent.com/developer/article/1178722

3、lua-nginx-module模塊裏ngx_lua的所有指令以及可用ngx所有方法:http://www.04007.cn/article/430.html4、

發表評論
所有評論
還沒有人評論,想成為第一個評論的人麼? 請在上方評論欄輸入並且點擊發布.
相關文章