多参考pdf文档
数据加载模块(DataLoader):
elasticsearch,mongodb
统计推荐模块(StatisticRecommender):
只用到mongodb
LFM、ALS模块(OfflineRecommender):
只用到mongodb
这一步完了之后,跑完了ALSTrainer之后,跑一下OfflineRecommender
实时推荐模块(streamingrecommender):
mongodb,redis,kafka,zookeeper
基于内容的推荐模块:
mongodb,kafka,flume,elasticsearch,redis
注意在整个系统大联调的时候要在kafka再创建一个topic: log,他视频没有讲
./bin/kafka-console-producer.sh --broker-list localhost:9092 --topic log
之前创建的recommender的topic不用删,没事
mongodb中
AverageMovie是统计推荐
ContentMovieRecs是内容的推荐
Movie是原始数据
MovieRecs是隐语义模型计算出来的相似度
UserRecs是离线的推荐
这个颜色这样,说明只是把它拷贝到这个项目里面了,但还没有加入到maven项目中
因为这个父项目的pom文件还不认识它
所以我们需要给它添加进去
先启动zookeeper,再启动kafka
启动kafka时,最好先不用加-daemon静默启动,否则如果有错的话你都不知道
报错①:
WARN [Producer clientId=console-producer] Connection to node -1 (localhost
/127.0.0.1:9092) could not be established. Broker may not be available. (org.apache.kafka.clients.Ne
tworkClient)
原因:kafka启动出错,没有启动起来,就是在kafka-server-start这一步的问题,都还没有到kafka-console-producer这一步,kafka启动的问题见报错②
报错②:
org.apache.kafka.common.KafkaException: Found directory /home/ubuntu/kafka/logs-1/zookeeper, 'zookee
per' is not in the form of topic-partition or topic-partition.uniqueId-delete (if marked for deletio
n).
Kafka's log directories (and children) should only contain Kafka topic data.
原因:我设定的kafka日志存放路径时/home/ubuntu/kafka/logs-1
但由于之前启动过,logs-1文件夹里面已经有文件了,所以把logs-1文件夹删除就好了
或者如果觉得不保险就重命名一下 mv logs-1 logs-2
报错③:
Error while fetching metadata with correlation id 1 : {recommender=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.NetworkClient)
原因:kafka的配置server.properties中把advertised.listener给注释掉了,去掉注释就好了
kafka的server.properties的配置
# 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. # see kafka.server.KafkaConfig for additional details and defaults ############################# Server Basics ############################# # The id of the broker. This must be set to a unique integer for each broker. broker.id=0 ############################# Socket Server Settings ############################# # The address the socket server listens on. It will get the value returned from # java.net.InetAddress.getCanonicalHostName() if not configured. # FORMAT: # listeners = listener_name://host_name:port # EXAMPLE: # listeners = PLAINTEXT://your.host.name:9092 listeners=PLAINTEXT://127.0.0.1:9092 # Hostname and port the broker will advertise to producers and consumers. If not set, # it uses the value for "listeners" if configured. Otherwise, it will use the value # returned from java.net.InetAddress.getCanonicalHostName(). advertised.listeners=PLAINTEXT://127.0.0.1:9092 # Maps listener names to security protocols, the default is for them to be the same. See the config documentation for more details #listener.security.protocol.map=PLAINTEXT:PLAINTEXT,SSL:SSL,SASL_PLAINTEXT:SASL_PLAINTEXT,SASL_SSL:SASL_SSL # The number of threads that the server uses for receiving requests from the network and sending responses to the network num.network.threads=3 # The number of threads that the server uses for processing requests, which may include disk I/O num.io.threads=8 # The send buffer (SO_SNDBUF) used by the socket server socket.send.buffer.bytes=102400 # The receive buffer (SO_RCVBUF) used by the socket server socket.receive.buffer.bytes=102400 # The maximum size of a request that the socket server will accept (protection against OOM) socket.request.max.bytes=104857600 ############################# Log Basics ############################# # A comma separated list of directories under which to store log files log.dirs=/home/ubuntu/kafka/logs-1 # The default number of log partitions per topic. More partitions allow greater # parallelism for consumption, but this will also result in more files across # the brokers. num.partitions=1 # The number of threads per data directory to be used for log recovery at startup and flushing at shutdown. # This value is recommended to be increased for installations with data dirs located in RAID array. num.recovery.threads.per.data.dir=1 ############################# Internal Topic Settings ############################# # The replication factor for the group metadata internal topics "__consumer_offsets" and "__transaction_state" # For anything other than development testing, a value greater than 1 is recommended for to ensure availability such as 3. offsets.topic.replication.factor=1 transaction.state.log.replication.factor=1 transaction.state.log.min.isr=1 ############################# Log Flush Policy ############################# # Messages are immediately written to the filesystem but by default we only fsync() to sync # the OS cache lazily. The following configurations control the flush of data to disk. # There are a few important trade-offs here: # 1. Durability: Unflushed data may be lost if you are not using replication. # 2. Latency: Very large flush intervals may lead to latency spikes when the flush does occur as there will be a lot of data to flush. # 3. Throughput: The flush is generally the most expensive operation, and a small flush interval may lead to excessive seeks. # The settings below allow one to configure the flush policy to flush data after a period of time or # every N messages (or both). This can be done globally and overridden on a per-topic basis. # The number of messages to accept before forcing a flush of data to disk #log.flush.interval.messages=10000 # The maximum amount of time a message can sit in a log before we force a flush #log.flush.interval.ms=1000 ############################# Log Retention Policy ############################# # The following configurations control the disposal of log segments. The policy can # be set to delete segments after a period of time, or after a given size has accumulated. # A segment will be deleted whenever *either* of these criteria are met. Deletion always happens # from the end of the log. # The minimum age of a log file to be eligible for deletion due to age log.retention.hours=168 # A size-based retention policy for logs. Segments are pruned from the log unless the remaining # segments drop below log.retention.bytes. Functions independently of log.retention.hours. #log.retention.bytes=1073741824 # The maximum size of a log segment file. When this size is reached a new log segment will be created. log.segment.bytes=1073741824 # The interval at which log segments are checked to see if they can be deleted according # to the retention policies log.retention.check.interval.ms=300000 ############################# Zookeeper ############################# # Zookeeper connection string (see zookeeper docs for details). # This is a comma separated host:port pairs, each corresponding to a zk # server. e.g. "127.0.0.1:3000,127.0.0.1:3001,127.0.0.1:3002". # You can also append an optional chroot string to the urls to specify the # root directory for all kafka znodes. zookeeper.connect=127.0.0.1:2181 # Timeout in ms for connecting to zookeeper zookeeper.connection.timeout.ms=6000 ############################# Group Coordinator Settings ############################# # The following configuration specifies the time, in milliseconds, that the GroupCoordinator will delay the initial consumer rebalance. # The rebalance will be further delayed by the value of group.initial.rebalance.delay.ms as new members join the group, up to a maximum of max.poll.interval.ms. # The default value for this is 3 seconds. # We override this to 0 here as it makes for a better out-of-the-box experience for development and testing. # However, in production environments the default value of 3 seconds is more suitable as this will help to avoid unnecessary, and potentially expensive, rebalances during application startup. group.initial.rebalance.delay.ms=0
整个系统大联调时,agent.log有了数据而Application和StreamingRecommender没有数据
将flume ctrl+c关闭后再重启就之前的好几条数据都来了
但flume好像不能实时,关掉重启之后能传送之前的几条数据,不知道为啥.......
./bin/kafka-topics.sh --zookeeper localhost:2181 --list ./bin/kafka-server-start.sh -daemon ./config/server.properties ./bin/kafka-console-producer.sh --broker-list localhost:9092 --topic recommender 1|1271|4.5|1554276432